pixi: Use a single CMAKE_BUILD_TYPE env variable to set the build type #1793
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AntonioViscomi
approved these changes
Feb 5, 2025
There was a problem hiding this comment.
The build is not overwriting the cmake options anymore. Thanks!
C:\Users\aviscomi\robotology-superbuild>pixi run build -j16
✨ Pixi task (configure in default): cmake -G Ninja -S . -B .buildcc @traversaro
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
@AntonioViscomi was reporting some problem when trying to switch some subprojects of the superbuild to
RelWithDebInfo. By looking at the pixi.toml, I noticed that the information on the CMake build type was duplicated everywhere, while probably it is simpler to just set once theCMAKE_BUILD_TYPEenv variable.