Skip to end of metadata
Go to start of metadata

In general, WAF is a complete command line based build system. All build operations are executed via specific parameters, also for builds initiated by visual studio.

*NotePlease keep in mind that the command line interface targets more advanced users, normally WAF handles all required operations automatically.

This page tries to introduce the command line interface.

Command Line Interface:

The general layout of the command line interface is:

cry_waf.exe <command> <options_0> ... <option_N>

The command line interface more or less has three different modes:

  • Utility Command: Whenever WAF is executed without any parameters, a console menu is shown. This menu allows to perform various tasks (e.g. install the WAF Visual Studio Addin)
  • Non-Build-Commands: Those commands are not directly related to building the projects. Instead those provide helper functions like generating a visual studio solution.
  • Build-Commands: Those commands are responsible to perform a build of the project.

For a list of commands see WAF Commands.
For a list of options see WAF Build Options.

*Note*: Please keep in mind that all of those commands are case-sensitive.

Utility Command:

This is the screen shown when cry_waf.exe is executed without any commands or parameters.

WAF Commands

Exit:

Quits the cry_waf utilities dialog.

Regenerate the Visual Studio Solution:

This command can be used to cause a regeneration of the current visual studio solution and all of its projects, for example to see newly added files or projects in the solution.
(If not performed manually, WAF will automatically perform this step after a successful build)

Regenerate Uber Files:

This command can be used to update all generated uber files in case new files were added, old ones removed, or the current uber files became corrupted.
(If not performed manually, WAF will automatically perform this step after a successful build)

Run Configure Step:

This command can be used to run the 'configure' step, which collects and caches build specific compiler settings.
(If not performed manually, WAF will automatically perform this step after a successful build)

  • No labels