diff options
author | Brad King <brad.king@kitware.com> | 2020-02-05 14:10:59 (GMT) |
---|---|---|
committer | Kitware Robot <kwrobot@kitware.com> | 2020-02-05 14:11:10 (GMT) |
commit | 56ddef613d2bf4c23ad40ef6f2102b515bbef3a3 (patch) | |
tree | 8751851e362c2bd9e316c4cda67a185299b6655a /Help/generator/Ninja Multi-Config.rst | |
parent | 94be195a5462f4d15e722333263f9a2eef09458f (diff) | |
parent | bd4ae2af0fe00813919c8188da7bb07d57ef3734 (diff) | |
download | CMake-56ddef613d2bf4c23ad40ef6f2102b515bbef3a3.zip CMake-56ddef613d2bf4c23ad40ef6f2102b515bbef3a3.tar.gz CMake-56ddef613d2bf4c23ad40ef6f2102b515bbef3a3.tar.bz2 |
Merge topic 'ninja-multi-cmake-build-no-config'
bd4ae2af0f Help: Make note of ninja -f argument in Ninja Multi-Config docs
79e5b3c46a Help: Explain new behavior of cmake --build in Ninja Multi-Config
16a4ba5b31 Ninja Multi-Config: Use build.ninja if cmake --build has no --config
2ac835b9f9 Refactor: Allow generators to decide default configuration for build
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4323
Diffstat (limited to 'Help/generator/Ninja Multi-Config.rst')
-rw-r--r-- | Help/generator/Ninja Multi-Config.rst | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/Help/generator/Ninja Multi-Config.rst b/Help/generator/Ninja Multi-Config.rst index 31e8ea9..11c59f2 100644 --- a/Help/generator/Ninja Multi-Config.rst +++ b/Help/generator/Ninja Multi-Config.rst @@ -11,10 +11,16 @@ 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 +configurations (with ``<Config>`` being the configuration name.) These files +are intended to be run with ``ninja -f build-<Config>.ninja``. No ``build.ninja`` file is generated by default (see below for how to generate it.) +``cmake --build . --config <Config>`` will always use ``build-<Config>.ninja`` +to build. If no ``--config`` argument is specified, ``cmake --build .`` will +default to ``build-Debug.ninja``, unless a ``build.ninja`` is generated (see +below), in which case that will be used instead. + Each ``build-<Config>.ninja`` file contains ``<target>`` targets as well as ``<target>:<Config>`` targets, where ``<Config>`` is the same as the configuration specified in ``build-<Config>.ninja`` Additionally, if |