- This topic has 3 replies, 2 voices, and was last updated 3 years, 1 month ago by
.
-
Posts
-
It seems that on CMake projects, we have lost the ability to specify different Custom build steps for the different configurations. For example, we used to run some file processing only in Release mode but with our latest CMake project, the custom steps seem to be shared between all the different project configuration. Is that a know issue?
Hi,
This is correct. The Advanced CMake Project Subsystem reuses the same set of settings for multiple targets and configurations, so the custom action lists will run for all configurations.
To make it easier to support your scenario, we have added a “condition” parameter to the “Reference a reusable action list” action. E.g. you can set it to “$(Configuration)” = “Debug” to only run the reference list when building/debugging the Debug configuration.
Please try this build: VisualGDB-5.6.1.4033.msi
Works well (once I understood how to create a reusable action list!) – Thanks a lot
Hopefully CMake is here to stay since this is our 3rd project migration!
No worries. CMake has several advantages to any other build system we are aware of, and is actively maintained, so we wouldn’t expect it to disappear anytime soon.
On the VisualGDB side, it is now the main and the recommended build system for embedded projects because because of the great separation of project-level, target-level and platform-level settings it offers.
- You must be logged in to reply to this topic.