Skip to end of metadata
Go to start of metadata

Overview

We have tried to make it as easy as possible to migrate from WAF to CMake. This section will explain the process of converting a project.

Important Differences

While we have tried to keep things as similar as possible, there are a few differences that should be kept in mind when converting.

  • When building static libraries, WAF will create a list of module users and then build each library multiple times if different module users specify differing compilation flags.
    CMake will only build each static library once, with a single set of compilation flags.
  • In WAF, static libraries were built to object files and then these object files were linked into each DLL that made use of them.
    In CMake, static libraries go through an intermediate .a/.lib file. This may cause differences at link time.
  • If you are using Incredibuild for building, WAF would previously provide the option to invoke Incredibuild for you.
    With CMake, you must invoke Incredibuild manually.
  • If you include Sandbox in your solution, only Debug and Profile builds are possible. You have to create a solution without Sandbox in order to build Release binaries.
  • CMake does not provide a Performance configuration; only Debug, Profile and Release are available.

Specifying Source Files

A key difference between the structure of our WAF and CMake scripts is that the list of source files is embedded into the same CMakeLists.txt file as the project extension, rather than being stored in external files.

To assist with converting over existing file lists, we provide a tool called waf2cmake, located in Tools\CMake\waf2cmake.

If you run the batch file run_waf2cmake.bat, the tool will automatically traverse all WAF modules defined through Code\wscript and Engine\wscript. If a module directory has a CMakeLists.txt, that file will be updated to match the WAF file lists. The tool can also try to check out these files to the default changelist in Perforce, using the command-line Perforce client.

If you have existing game projects not referenced from either of these files, you can use the --paths command-line option to parse additional directories. By default, the tool will parse Code/GameMono, Code/GameSDK and Code/GameZero.

Icon

The 5.3.0 release requires you to modify the batch file to add these options. 5.3.1 will add the ability to pass these extra arguments directly to the batch file.

To avoid accidentally overwriting critical parts of the file, waf2cmake only replaces text between specific, pre-defined tokens. If you are adding a custom module that was previously defined with WAF, and you wish to use waf2cmake to populate the file list, put the following text near the top of your CMakeLists.txt before running waf2cmake:

When run, waf2cmake will replace the contents of this block with the file lists.

Icon

waf2cmake only updates the list of source files. Settings for the individual project must still be maintained manually.

Converting projects

We will use the following module as an example. While this does not cover all possible cases, it should provide enough insight into how we have performed these conversions.

 

We will assume you have already created an empty CMakeLists.txt file in this directory, added the tokens mentioned in the previous sections, and run waf2cmake. This will automatically have taken care of the file_list and win_file_list arguments for us.

We start by declaring the module. This is done using the CryEngineModule function, which also lets us specify the precompiled header and solution folder. Place this at the end of the file, after the #END-FILE-LIST marker.

 

This will automatically pick up the appropriate list of source files for your module based on the source files listed earlier in the file, as inserted by waf2cmake. Source files which are not relevant for your current build target will show up in the solution if they are available, but they will not be compiled.

Next, we will convert includes and module_provides:

${THIS_PROJECT} is a variable that gets set by CryEngineModule, providing an easy way of referring to the module most recently defined this way. PUBLIC and INTERFACE specify where this information gets applied: PUBLIC is used for the module itself and anything that links to it, while INTERFACE only applies to other modules that link to your module. Since our module exposes the same include directory as it uses, we can take advantage of this and combing these using PUBLIC.

For use_module, we just need to link to the corresponding library.

In line with PUBLIC and INTERFACE from the previous part, PRIVATE signifies that this only applies to the module itself, not to anything that links to the module.

Next, we have a Windows-specific section, so we need to surround further directives with this block:

Icon

WIN32 is also set on 64-bit Windows builds, but being explicit can help serve as a reminder that this part applies to both.

Here, we can link to shell32 in the same way we linked to lua previously:

For libpath, CMake has no direct equivalent - instead, you are supposed to provide the full path to the module in question. In some cases, however, this may not be straightforward or desirable, so you can still emulate this directive. We need different folders for each platform, so we will separate the common parts out and add the platform-specific part separately:

Icon

The space after the opening quotation mark is required to ensure correct operation.

Finally, we need to specify linking to MySDK. For this, we use CMake's generator expressions. In this case, we will use one expression to match our debug-only library, and another to match the other configurations:

Icon

When linking multiple libraries to a specific configuration, each library must have its own generator expression. Spaces in generator expressions may not work reliably.

With that, the module conversion is complete. The last step is to make CMake include the module. For this, we go to Tools\CMake and add a matching add_subdirectory directive to the appropriate Build*.cmake file. Since this is an engine module, open BuildEngine.cmake and add the following line in an appropriate place:

 

 
  • No labels