Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
G
glslang
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Chen Yisong
glslang
Commits
5fcfae83
Commit
5fcfae83
authored
Sep 26, 2016
by
John Kessenich
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
README update for GitLab appropriateness.
parent
abbe5c8c
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
47 deletions
+4
-47
README.md
README.md
+4
-47
No files found.
README.md
View file @
5fcfae83
Also see the Khronos landing page for glslang as a reference front end:
Private version of glslang for Khronos-internal development.
https://www.khronos.org/opengles/sdk/tools/Reference-Compiler/
MRs to add functionality must be accompanied by simple regression tests, which are supplied with the gtests framework.
See instructions below.
The above page includes where to get binaries, and is kept up to date
regarding the feature level of glslang.
glslang
=======
[

](https://travis-ci.org/KhronosGroup/glslang)
[

](https://ci.appveyor.com/project/Khronoswebmaster/glslang/branch/master)
An OpenGL and OpenGL ES shader front end and validator.
There are several components:
1.
A GLSL/ESSL front-end for reference validation and translation of GLSL/ESSL into an AST.
2.
An HLSL front-end for translation of a broad generic HLL into the AST.
3.
A SPIR-V back end for translating the AST to SPIR-V.
4.
A standalone wrapper,
`glslangValidator`
, that can be used as a command-line tool for the above.
How to add a feature protected by a version/extension/stage/profile: See the
comment in
`glslang/MachineIndependent/Versions.cpp`
.
Tasks waiting to be done are documented as GitHub issues.
Execution of Standalone Wrapper
-------------------------------
To use the standalone binary form, execute
`glslangValidator`
, and it will print
a usage statement. Basic operation is to give it a file containing a shader,
and it will print out warnings/errors and optionally an AST.
The applied stage-specific rules are based on the file extension:
*
`.vert`
for a vertex shader
*
`.tesc`
for a tessellation control shader
*
`.tese`
for a tessellation evaluation shader
*
`.geom`
for a geometry shader
*
`.frag`
for a fragment shader
*
`.comp`
for a compute shader
There is also a non-shader extension
*
`.conf`
for a configuration file of limits, see usage statement for example
Building
Building
--------
--------
...
@@ -53,7 +10,7 @@ Building
...
@@ -53,7 +10,7 @@ Building
*
[
CMake
][
cmake
]
: for generating compilation targets.
*
[
CMake
][
cmake
]
: for generating compilation targets.
*
[
bison
][
bison
]
: _optional_, but needed when changing the grammar (glslang.y).
*
[
bison
][
bison
]
: _optional_, but needed when changing the grammar (glslang.y).
*
[
googletest
][
googletest
]
:
_optional_, but should use
if making any changes to glslang.
*
[
googletest
][
googletest
]
:
needed
if making any changes to glslang.
### Build steps
### Build steps
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment