Use Ninja multi-config with CMake #4517
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Prelude
Changes Proposed
Issues addressed:
Using Ninja multi-config allows us to build in multiple configurations, such as Debug, RelWithDebInfo and Release.
Currently, one needs to pass the build type prior to generating makefiles, with
cmake --preset default -DCMAKE_BUILD_TYPE=<buildtype>
followed bycmake --build --preset default
, and rebuilding with a different config required regenerating makefiles.Now, a clearer invocation of
cmake
is possible withcmake --preset default
to generate makefiles, and thencmake --build --preset default --config <buildtype>
is possible without regenerating makefiles, and in separate folders so that one can maintain multiple builds (for debugging and running in production, for example)