QSB Manual
qsb is a command-line tool provided by the Qt Shader Tools module. It integrates third-party libraries such as glslang and SPIRV-Cross, optionally invokes external tools, such as, fxc or spirv-opt, and generates .qsb files. Additionally, it can be used to inspect the contents of a .qsb package.
Usage: qsb [options] file
Qt Shader Baker (using QShader from Qt 6.0.0)
Options:
-?, -h, --help Displays help on commandline options.
--help-all Displays help including Qt specific options.
-v, --version Displays version information.
-b, --batchable Also generates rewritten vertex shader for Qt
Quick scene graph batching.
--zorder-loc <location> The extra vertex input location when rewriting
for batching. Defaults to 7.
--glsl <versions> Comma separated list of GLSL versions to
generate. (for example, "100 es,120,330")
--hlsl <versions> Comma separated list of HLSL (Shader Model)
versions to generate. F.ex. 50 is 5.0, 51 is 5.1.
--msl <versions> Comma separated list of Metal Shading Language
versions to generate. F.ex. 12 is 1.2, 20 is 2.0.
-g Generate full debug info for SPIR-V and DXBC
-O Invoke spirv-opt to optimize SPIR-V for
performance
-o, --output <filename> Output file for the shader pack.
-c, --fxc In combination with --hlsl invokes fxc to store
DXBC instead of HLSL.
-t, --metallib In combination with --msl builds a Metal library
with xcrun metal(lib) and stores that instead of
the source.
-D, --define <name[=value]> Define macro
-p, --per-target Enable per-target compilation. (instead of
source->SPIRV->targets, do source->SPIRV->target
separately for each target)
-d, --dump Switches to dump mode. Input file is expected to
be a shader pack.
-x, --extract <what> Switches to extract mode. Input file is expected
to be a shader pack. Result is written to the
output specified by -o. Pass -b to choose the
batchable variant.
<what>=reflect|spirv.<version>|glsl.<version>|...
Arguments:
file Vulkan GLSL source file to compile
Modes of Operation
There are three major modes of operation:
.qsbfile generation..qsbfile inspection. For example,qsb -d myshader.frag.qsbwill print the reflection metadata (in JSON form) and the included shaders.- Extraction mode. This allows writing a given shader from an existing
.qsbfile into a separate file. For examples,qsb -x spirv.100 -o myshader.spv myshader.frag.qsbwrites the SPIR-V binary intomyshader.spv.
Example
Take the following fragment shader:
#version 440
layout(location = 0) in vec2 v_texcoord;
layout(location = 0) out vec4 fragColor;
layout(binding = 1) uniform sampler2D tex;
layout(std140, binding = 0) uniform buf {
float uAlpha;
};
void main()
{
vec4 c = texture(tex, v_texcoord);
fragColor = vec4(c.rgb, uAlpha);
}
Executing qsb -o shader.frag.qsb shader.frag results in generating shader.frag.qsb. Inspecting this file with qsb -d shader.frag.qsb gives us:
Stage: Fragment
QSB_VERSION: 5
Has 1 shaders: (unordered list)
Shader 0: SPIR-V 100 [Standard]
Reflection info: {
"combinedImageSamplers": [
{
"binding": 1,
"name": "tex",
"set": 0,
"type": "sampler2D"
}
],
"inputs": [
{
"location": 0,
"name": "v_texcoord",
"type": "vec2"
}
],
"localSize": [
0,
0,
0
],
"outputs": [
{
"location": 0,
"name": "fragColor",
"type": "vec4"
}
],
"uniformBlocks": [
{
"binding": 0,
"blockName": "buf",
"members": [
{
"name": "uAlpha",
"offset": 0,
"size": 4,
"type": "float"
}
],
"set": 0,
"size": 4,
"structName": "_27"
}
]
}
Shader 0: SPIR-V 100 [Standard]
Entry point: main
Contents:
Binary of 864 bytes
By default only SPIR-V is generated, so an application using this shader package would only be functional with Vulkan. Let's make it more useful:
qsb --glsl "100 es,120,150" --hlsl 50 --msl 12 -o shader.frag.qsb shader.frag
This leads to generating a shader package that makes it suitable for OpenGL, Direct 3D, and Metal as well. The features used in this shader are basic, and even GLSL ES 100 (the shading language of OpenGL ES 2.0) is suitable.
Inspecting the result shows:
Stage: Fragment
QSB_VERSION: 5
Has 6 shaders: (unordered list)
Shader 0: GLSL 120 [Standard]
Shader 1: HLSL 50 [Standard]
Shader 2: GLSL 100 es [Standard]
Shader 3: MSL 12 [Standard]
Shader 4: SPIR-V 100 [Standard]
Shader 5: GLSL 150 [Standard]
Reflection info: {
... <same as above>
}
Shader 0: GLSL 120 [Standard]
Entry point: main
Contents:
#version 120
struct buf
{
float uAlpha;
};
uniform buf _27;
uniform sampler2D tex;
varying vec2 v_texcoord;
void main()
{
vec4 c = texture2D(tex, v_texcoord);
gl_FragData[0] = vec4(c.xyz, _27.uAlpha);
}
************************************
Shader 1: HLSL 50 [Standard]
Entry point: main
Native resource binding map:
0 -> [0, -1]
1 -> [0, 0]
Contents:
cbuffer buf : register(b0)
{
float _27_uAlpha : packoffset(c0);
};
Texture2D<float4> tex : register(t0);
SamplerState _tex_sampler : register(s0);
static float2 v_texcoord;
static float4 fragColor;
struct SPIRV_Cross_Input
{
float2 v_texcoord : TEXCOORD0;
};
struct SPIRV_Cross_Output
{
float4 fragColor : SV_Target0;
};
void frag_main()
{
float4 c = tex.Sample(_tex_sampler, v_texcoord);
fragColor = float4(c.xyz, _27_uAlpha);
}
SPIRV_Cross_Output main(SPIRV_Cross_Input stage_input)
{
v_texcoord = stage_input.v_texcoord;
frag_main();
SPIRV_Cross_Output stage_output;
stage_output.fragColor = fragColor;
return stage_output;
}
************************************
...
Shader 3: MSL 12 [Standard]
Entry point: main0
Native resource binding map:
0 -> [0, -1]
1 -> [0, 0]
Contents:
#include <metal_stdlib>
#include <simd/simd.h>
using namespace metal;
struct buf
{
float uAlpha;
};
struct main0_out
{
float4 fragColor [[color(0)]];
};
struct main0_in
{
float2 v_texcoord [[user(locn0)]];
};
fragment main0_out main0(main0_in in [[stage_in]], constant buf& _27 [[buffer(0)]], texture2d<float> tex [[texture(0)]], sampler texSmplr [[sampler(0)]])
{
main0_out out = {};
float4 c = tex.sample(texSmplr, in.v_texcoord);
out.fragColor = float4(c.xyz, _27.uAlpha);
return out;
}
************************************
...
This package can now be used by Qt Quick with all supported graphics APIs: Vulkan, Direct 3D, Metal, OpenGL, and OpenGL ES. At run time the appropriate shader is picked up automatically by the Qt Rendering Hardware Interface that sits underneath Qt Quick and Qt Quick 3D.
Besides translating the SPIR-V bytecode back to higher level source code, the system takes care of additional problems, such as ensuring correct mapping of SPIR-V binding numbers onto native resources. For example, with HLSL we saw a section like this above:
Native resource binding map: 0 -> [0, -1] 1 -> [0, 0]
Internally this allows mapping a SPIR-V style binding point 0 to the HLSL register b0 and binding 1 to t0 and s0. This helps making the differences in resource bindings between the various shading languages transparent to the users of the Rendering Hardware Interface, and allows everything in Qt to operate with Vulkan/SPIR-V style binding points as they are specified in the original Vulkan-style GLSL source code.
Shader Types
The type of shader is deduced from the input file extension. Thus, the extension must be one of the following:
.vert- for vertex shaders.frag- for fragment (pixel) shaders.comp- for compute shaders
Shading Languages and Versions
SPIR-V 1.0 is always generated. What gets generated in addition depends on the command-line arguments --glsl, --hlsl, and --msl.
These parameters are all followed by a comma-separated list. The list must include GLSL-style version numbers, with an optional suffix (es, indicating GLSL ES). The space between the suffix and the version is optional (not having the space can help avoiding the need for quoting).
For example, Qt Quick's built-in materials (the shaders backing items, such as Image, Text, Rectangle) all prepare their shaders with --glsl "100 es,120,150" --hlsl 50 --msl 12. This makes them compatible with OpenGL ES 2.0 and higher, OpenGL 2.1 and higher, and OpenGL core profile contexts of version 3.2 and higher.
If the shader uses functions or constructs that do not have an equivalent in the specified targets, qsb will fail. If that is the case, the targets will need to be adjusted, and this also means that the application's minimum system requirements get adjusted implicitly. As an example, take the textureLod GLSL function that is only available with OpenGL ES 3.0 and up (meaning GLSL ES 300 or higher). When requesting GLSL 300 es instead of 100 es, qsb will succeed, but the application using that .qsb file will now require OpenGL ES 3.0 or higher and will not be compatible with OpenGL ES 2.0 based systems.
Another obvious example of this are compute shaders: .comp shaders will need to specify --glsl 310es,430 as compute shaders are only available with OpenGL ES 3.1 or newer and OpenGL 4.3 or newer.
Adjusting the shader model version for HLSL, or the Metal Shading Language version is expected to be needed rarely. Shader Model 5.0 (--hlsl 50) and MSL 1.2 (--msl 12) will typically be sufficient.
Qt Quick Scene Graph Batching
The Qt Quick Scene Graph's renderer supports batching of geometry to reduce the number of draw calls. See the Scene Graph pages for details. This relies on injecting code to the vertex shader's main() function. In Qt 5.x this happened at run time, by modifying the supplied GLSL vertex shader code. In Qt 6 that is not an option. Instead, batchable variants of vertex shaders can be built by the qsb tool. This is requested by the -b argument. When the input is not a vertex shader with .vert extension, it has no effect. For vertex shaders however, it will lead to generating to versions for each target. Qt Quick will then automatically pick the right variant (standard or batchable) at run time.
Note: Applications do not have to concern themselves with the details of batching. They must simply ensure that -b (or the equivalent BATCHABLE keyword if using the CMake integration) is specified when processing the vertex shaders. This is relevant only for Qt Quick shaders used with ShaderEffect or QSGMaterialShader.
Take the following example vertex shader:
#version 440
layout(location = 0) in vec4 position;
layout(location = 1) in vec2 texcoord;
layout(location = 0) out vec2 v_texcoord;
layout(std140, binding = 0) uniform buf {
mat4 mvp;
} ubuf;
out gl_PerVertex { vec4 gl_Position; };
void main()
{
v_texcoord = texcoord;
gl_Position = ubuf.mvp * position;
}
Running qsb -b --glsl 330 -o example.vert.qsb example.vert leads to:
Stage: Vertex
QSB_VERSION: 5
Has 4 shaders: (unordered list)
Shader 0: GLSL 330 [Standard]
Shader 1: GLSL 330 [Batchable]
Shader 2: SPIR-V 100 [Standard]
Shader 3: SPIR-V 100 [Batchable]
Reflection info: {
...
Note how all target languages and versions now exist in two variants: Standard and a slightly modified Batchable.
Invoking External Tools
qsb can invoke certain external tools. These fall into two categories: tools for performing optimizations on the shader bytecode (SPIR-V), and platform-specific tools to perform the first phase of shader compilation, from source to some intermediate bytecode format.
These are enabled by the following command-line options:
-O- invokesspirv-optas a post-processing step on the SPIR-V binary. The.qsbfile will include the optimized version. This assumes thatspirv-optis available on the system (for example, from the Vulkan SDK) and ready to be invoked.-cor--fxc- invokesfxc.exe, the Direct 3D shader compiler. The resultingDXBC(DirectX Byte Code) data is what gets stored in the.qsbfile instead of HLSL. Qt will automatically pick it up at run time, so it is up to the.qsbfile's creator to decide what to include, HLSL source or the intermediate format. Whenever possible, prefer the latter since it eliminates the need for parsing and HLSL source at run time, leading to potentially significant performance gains upon graphics pipeline creation. The downside is that this argument can only be used whenqsbis being run on Windows.-tor--metallib- invokves the appropriate XCode Metal tools to generate a .metallib file and includes that in the.qsbpackage instead of the MSL source code. This option is only available whenqsbis running on macOS.
Other Options
-D- defines a macro. This allows using #ifdef and similar in the GLSL source code.-g- enables generating full debug information for SPIR-V, thus enabling tools like RenderDoc to display the full source when inspecting a pipeline or when performing vertex or fragment debugging. Also has an effect for Direct 3D when-cis specified, becausefxcis then instructed to include debug information in the generated intermediate bytecode.