Peter
Reputation: 3163
cmake: separate multi-config build artifacts?
I don't quite understand the purpose and/or usage of the "Ninja Multi-Config" generator in CMake. When using it and specifying CMAKE_CONFIGURATION_TYPES="Debug;Release", the build directory will then contain build-Debug.ninja and build-Release.ninja. But when actually running e.g. ninja -f build-Debug.ninja, the generated build artifacts end up where they normally would without using multi-config. That means that if I first run the debug and then the release build the latter will overwrite the former! That seems pointless to me, in that case why not just generate one config to begin with? Is there a way to be able to build both configurations simultaneously in the same build directory?
Upvotes: 0
Views: 38
Answers (0)
Related Questions
- Looking for a 'cmake clean' command to clear up CMake output
- What is the proper way to handle `CMAKE_INSTALL_PREFIX` when using the Ninja Multi-Config cmake generator?
- Ninja equivalent of Make's "build from this directory down" feature (with CMake)?
- How to make a multi-config generator behave like a single-config generator in a project using ExternalProjects?
- CMake multi config generator on multi platform
- Debug vs Release in CMake
- How-to use an existing CMakeCache.txt for the "Ninja Multi-Config" generator in Microsoft Visual Studio 2019?
- CMake configuration specific library name when using multi-config generators
- Cmake: Specifiy config specific settings for multi-config cmake project
- CMake - Accessing configuration parameters of multiple-configuration generators