diff options
author | Kyle Edwards <kyle.edwards@kitware.com> | 2019-11-27 16:58:02 (GMT) |
---|---|---|
committer | Kyle Edwards <kyle.edwards@kitware.com> | 2019-12-13 15:52:07 (GMT) |
commit | 8c062f9d9986560588bbc5b7cffbbf3de940cc02 (patch) | |
tree | 82c2f2de0c29fae4d57970a71edb7446066504a0 /Help/generator | |
parent | e0478cc64623fbfcb7dcd748f27b94cc8473fa1a (diff) | |
download | CMake-8c062f9d9986560588bbc5b7cffbbf3de940cc02.zip CMake-8c062f9d9986560588bbc5b7cffbbf3de940cc02.tar.gz CMake-8c062f9d9986560588bbc5b7cffbbf3de940cc02.tar.bz2 |
Help: Add documentation and release notes for multi-config Ninja
Diffstat (limited to 'Help/generator')
-rw-r--r-- | Help/generator/Ninja Multi-Config.rst | 74 | ||||
-rw-r--r-- | Help/generator/Ninja.rst | 8 |
2 files changed, 81 insertions, 1 deletions
diff --git a/Help/generator/Ninja Multi-Config.rst b/Help/generator/Ninja Multi-Config.rst new file mode 100644 index 0000000..71cc392 --- /dev/null +++ b/Help/generator/Ninja Multi-Config.rst @@ -0,0 +1,74 @@ +Ninja Multi-Config +------------------ + +Generates multiple ``build-<Config>.ninja`` files. + +This generator is very much like the :generator:`Ninja` generator, but with +some key differences. Only these differences will be discussed in this +document. + +Unlike the :generator:`Ninja` generator, ``Ninja Multi-Config`` generates +multiple configurations at once with :variable:`CMAKE_CONFIGURATION_TYPES` +instead of only one configuration with :variable:`CMAKE_BUILD_TYPE`. One +``build-<Config>.ninja`` file will be generated for each of these +configurations (with ``<Config>`` being the configuration name.) No +``build.ninja`` file is generated, unless +:variable:`CMAKE_NINJA_MULTI_DEFAULT_BUILD_TYPE` is specified. You must specify +the desired ``build-<Config>.ninja`` file with ``ninja -f``. Running +``cmake --build . --config <Config> --target <target>`` will run Ninja with +``build-<Config>.ninja`` as the ``-f`` file and ``<target>`` as the build +target. + +Executables and libraries of any configuration can be built regardless of which +``build-<Config>.ninja`` file is used, simply by specifying +``<target>:<Config>`` as the Ninja target. You can also specify +``<target>:all`` to build a target in all configurations. Each +``build-<Config>.ninja`` file will additionally have ``<target>`` targets which +are aliases for ``<target>:<Config>``. However, custom commands and custom +targets will always use the configuration specified in +``build-<Config>.ninja``. This is due to the fact that it is impossible in +Ninja for the same file to be output with different commands in the same build +graph. + +Consider the following example: + +.. code-block:: cmake + + cmake_minimum_required(VERSION 3.16) + project(MultiConfigNinja C) + + add_executable(generator generator.c) + add_custom_command(OUTPUT generated.c COMMAND generator generated.c) + add_library(generated ${CMAKE_BINARY_DIR}/generated.c) + +Now assume you configure the project with ``Ninja Multi-Config`` and run one of +the following commands: + +.. code-block:: shell + + ninja -f build-Debug.ninja generated + # OR + cmake --build . --config Debug --target generated + +This would build the ``Debug`` configuration of ``generator``, which would be +used to generate ``generated.c``, which would be used to build the ``Debug`` +configuration of ``generated``. + +But if you run the following instead: + +.. code-block:: shell + + ninja -f build-Release.ninja generated:Debug + # OR + cmake --build . --config Release --target generated:Debug + +This would build the ``Release`` configuration of ``generator``, which would be +used to generate ``generated.c``, which would be used to build the ``Debug`` +configuration of ``generated``. This is useful for running a release-optimized +version of a generator utility while still building the debug version of the +targets built with the generated code. + +As a convenience, ``Ninja Multi-Config`` offers a +:variable:`CMAKE_NINJA_MULTI_DEFAULT_BUILD_TYPE` setting. If this variable is +specified, a ``build.ninja`` file will be generated which points to the +specified ``build-<Config>.ninja`` file. diff --git a/Help/generator/Ninja.rst b/Help/generator/Ninja.rst index c75d2c4..275055d 100644 --- a/Help/generator/Ninja.rst +++ b/Help/generator/Ninja.rst @@ -1,7 +1,7 @@ Ninja ----- -Generates build.ninja files. +Generates ``build.ninja`` files. A ``build.ninja`` file is generated into the build tree. Use the ninja program to build the project through the ``all`` target and install the @@ -38,3 +38,9 @@ features have not been integrated into upstream Ninja. Kitware maintains a branch of Ninja with the required features on `github.com/Kitware/ninja`_. .. _`github.com/Kitware/ninja`: https://github.com/Kitware/ninja/tree/features-for-fortran#readme + +See Also +^^^^^^^^ + +The :generator:`Ninja Multi-Config` generator is similar to the ``Ninja`` +generator, but generates multiple configurations at once. |