For each XML file, a custom build target will be created which invokes a python script. When cmake runs to create the build files it will look for XML files in the source code directories. Also, since the shader generation runs as a normal build step, shader code will also be generated and validated in command line builds. The edit-compile-test cycle is only one or two seconds, depending on the link time of the demo code. The error messages are recognised, but double-clicking them doesn’t work.Īfter the GLSL compiler pass, a C++ header/source file pair will be created which contains the GLSL shader code and some C++ glue to make the shader accessible from the engine side. Unfortunately I couldn’t get error parsing to work in QtCreator on Linux. Any errors from the reference compiler are converted to a format which can be parsed by the IDE:Įrror parsing also works in Visual Studio:

When compiling the project, a custom build step will generate vertex- and fragment shaders for different GLSL versions and run them through the GLSL reference compiler.

Shader files are written in normal GLSL syntax with custom annotations (those and $ tags): Shader source files (*.shd) live in the IDE next to C++ files:

I recently played around with shader code generation and the GLSL reference compiler in Oryol.

Visual studio code format shader