BAILOPAN at 18:11, 10 August 2020

2020-08-10T18:11:14Z

BAILOPAN: /* Integration */

2016-09-26T04:39:04Z

‎Integration

BAILOPAN: Created page with "AMBuild has rudimentary support for compiling and integrating HLSL shaders into a C++ project, via Microsoft's FXC tool. FXC is a somewhat tricky tool because it compiles onl..."

2016-09-26T04:29:59Z

Created page with "AMBuild has rudimentary support for compiling and integrating HLSL shaders into a C++ project, via Microsoft's FXC tool. FXC is a somewhat tricky tool because it compiles onl..."

New page

AMBuild has rudimentary support for compiling and integrating HLSL shaders into a C++ project, via Microsoft's FXC tool.

FXC is a somewhat tricky tool because it compiles only one function at a time. This results in many, many output files, which become difficult to manage for developers and can slow down the compilation process. AMBuild addresses this by generating "unified" files for a collection of shaders. The unified file acts a single include and translation unit for generated shader code.

=Creating an HLSL job=

The HLSL job constructor can be accessed via <tt>builder.tools.FXC</tt>, which takes the following parameters:
* <tt>prefix</tt> - A prefix to use for naming unified files.
* <tt>namespace</tt> - An optional string containing a fully-qualified namespace. For example, if you pass 'game::shaders', unified source and header code will be wrapped in a "shaders" namespace, inside a "games" namespace.

This function will construct an FxcJob object, which has the following additional properties:
* <tt>listDefineName</tt> - Optional name for a compile-time macro that will be defined in the unified shader header. This macro (explained further below) allows iterating over defined shaders in the preprocessor.
* <tt>shaders</tt> - A list of shader translation units.

Each shader translation unit should be a dictionary with the following keys:
* <tt>'source'</tt> - Path to the HLSL source file.
* <tt>'variable'</tt> - HLSL generates shaders as byte blobs assigned to a variable. This specifies the prefix that AMBuild will use to name the variable. For example, if you specify 'ModelShader', AMBuild will assign the bytes to 'ModelShader_Bytes' and the length to 'ModelShader_Length'.
* <tt>'profile'</tt> - The Shader Model profile to use.
* <tt>'entrypoint'</tt> - Optional. If specified, the entrypoint function of the shader. If not specified, AMBuild assumes it is 'main'.

The FxcJob object can be added to the <tt>custom</tt> list of a C++ job.

==Example==
shaders = builder.tools.FXC('all-shaders', 'game::shaders')
shaders.listDefineName = 'SHADER_LIST'
shaders.shaders += [
{
'source': 'quad_vertex_shader.hlsl',
'variable': 'QuadVertexShader',
'profile': 'vs_5_0',
},
]

program.custom += [shaders]

=Outputs=
AMBuild's FXC tool will generate two files of note, using the prefix specified in the job constructor. For example, if the job's constructor specified 'all-shaders' as above, the following files will be generated:
* <tt>all-shaders-include.h</tt>
* <tt>all-shaders-bytecode.cxx</tt>

The include file declares two variables for every shader translation unit. Using the example above, it would contain the following:
* <tt>extern const uint8_t* QuadVertexShader_Bytes;</tt>
* <tt>extern const size_t QuadVertexShader_Length;</tt>

Respectively, these would contain the bytecode blob and blob length for each shader. The include file can be included from any C++ file in the binary - it's automatically placed in the include path.

The bytecode file provides definitions for all the variables declared in the include file. It is automatically added to the compilation step (and linker step), so you do not need to handle it.

=Integration=
With the example above, we also defined a <tt>listDefineName</tt>. This provides some metaprogramming potential without having to modify AMBuild. For example, we can do the following:

<pre>
#include "all-shaders-include.h"

ID3D11VertexShader* QuadVertexShader = nullptr;

void InitializeShaders(ID3D11Device* device)
{
# define CREATE_SHADER(prefix) d3d11->CreateVertexShader(prefix##_Bytes, prefix##_Length, &prefix);
SHADER_LIST(CREATE_SHADER)
# undef CREATE_SHADER
}
</pre>

Currently, the list define iterates over all shaders. As needed we can extend the tool to iterate over shader types as well, or to specify custom unifier methods.

@@ Line 22: / Line 22: @@
 ==Example==
 shaders = builder.tools.FXC('all-shaders', 'game::shaders')
 shaders.listDefineName = 'SHADER_LIST'
@@ Line 33: / Line 34: @@
 program.custom += [shaders]
 =Outputs=

@@ Line 57: / Line 57: @@
 void InitializeShaders(ID3D11Device* device)
+{
-# define CREATE_SHADER(prefix) d3d11->CreateVertexShader(prefix##_Bytes, prefix##_Length, &prefix);
+# define CREATE_SHADER(prefix) device->CreateVertexShader(prefix##_Bytes, prefix##_Length, &prefix);
    SHADER_LIST(CREATE_SHADER)
 # undef CREATE_SHADER

AMBuild FXC API - Revision history

BAILOPAN at 18:11, 10 August 2020

BAILOPAN: /* Integration */

BAILOPAN: Created page with "AMBuild has rudimentary support for compiling and integrating HLSL shaders into a C++ project, via Microsoft's FXC tool. FXC is a somewhat tricky tool because it compiles onl..."