This section focuses on all options that WAF accepts as parameters for the build command.
Most options can also be changed in the configuration files BinTemp/cry_waf.options.
Project Spec to use during compilation. This is a mandatory option. Please see WAF Spec Files for more info.
No Default Value.
The targets option can be used to only compile a single project instead of the full engine. When providing a target option only the specified projects are compiled and all of theirs required dependencies.
E.g. "cry_waf.exe build_win32_profile --target Cry3DEngine" can be used to only compile the Cry3DEngine for win32 in profile configuration.
This option specifies of Incredibuild Should be used for compilation.
The default value depends on the assigned Incredibuild licenses.
This option specifies of Incredibuild Should be used for compilation of windows platforms.
The default value depends on the assigned Incredibuild licenses.
This option specifies of Incredibuild Should be used for compilation of Orbis platforms.
The default value depends on the assigned Incredibuild licenses.
This option specifies of Incredibuild Should be used for compilation of Durango platforms.
The default value depends on the assigned Incredibuild licenses.
Number of parallel threads to create when compiling with incredibuild. Should be larger than the number of processors (64 in case of Incredibuild), but not too large.
The default currently is 128 threads. Don't increase it too much, since python doesn't handle such large thread numbers well.
Should WAF check if recode is enabled, and potentially adjust the compile command according to Recode requirements.
The default is True.
Do not show GUI. Only show command-line interface. Useful for build slaves or SSH connections.
The default is False.
During compilation, should the compiler be instructed to generate debug information?
The default is True.
Should, if those are provided, precompiled header be used during compilation?
*Note* Currently precompiled headers are automatically disabled for projects using uber files since they don't bring any performance benefit in this case.
The default is True.
During compilation, should uber files be used if they are provided?
The default is True.
Path into which all final build results (executables, dlls etc) from a win32 build are copied
The default is Bin32
Path into which all final build results (executables, dlls etc) from a win64 build are copied
The default is Bin64
Path into which all final build results (executables, dlls etc) from a linux32 build are copied
The default is BinLinux32
Path into which all final build results (executables, dlls etc) from a linux64 build are copied
The default is BinLinux64
Path into which all final build results (executables, dlls etc) from a darwin32 build are copied
The default is BinDarwin32
Path into which all final build results (executables, dlls etc) from a darwin64 build are copied
The default is BinDarwin64
Path into which all final build results (executables, dlls etc) from a Orbis build are copied
The default is BinOrbis
Path into which all final build results (executables, dlls etc) from a Durango build are copied
The default is BinDurango
Inform WAF to not ask about for user input. This flag is needed some the Visual Studio Output Tab doesn't accept inputs.
The default is True
During compilation, only actually compile files which match this file filter.
The default is ""
Instead of compiling a file, output all files included by the compiled file.
The default is False
Instead of compiling a file, show the preprocessed file.
The default is False
Instead of compiling a file, show the disassembly output.
The default is False
Specifiy a single file to write the output to. Used for --show-preprocessed and --show-disassembly
The default is ""
Try to load the overwrite file (BinTemp/cry_waf.configuration_overwrites) to change project configurations. (This file is generated by the Visual Studio Addin)
The default is "False"