View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0011830 | CMake | CMake | public | 2011-02-09 14:06 | 2016-06-10 14:31 | ||||
Reporter | Derek Bruening | ||||||||
Assigned To | Kitware Robot | ||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||
Status | closed | Resolution | moved | ||||||
Platform | Intel | OS | Windows | OS Version | 7 | ||||
Product Version | CMake 2.8.3 | ||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0011830: cmake --build and ctest_build() assume "Debug" is the default config for multi-config generators | ||||||||
Description | If I change CMAKE_CONFIGURATION_TYPES: set(CMAKE_CONFIGURATION_TYPES "Release" CACHE STRING "" FORCE) prior to project() so that the only config choice is "Release", and then I try to build via "cmake --build ." or ctest_build(), cmake tries to build the Debug config and ends up failing w/ an up-front invalid command line error message from devenv. The workaround requires knowing the available config types, i.e., there's no way to build the default: % cmake --build . --config Release Or I can construct the build command myself: devenv DynamoRIO.sln /build Release /project ALL_BUILD This also seems to work (at least w/ VS2008), so this could be one way to fix this: devenv DynamoRIO.sln /build "" /project ALL_BUILD For me to use these I have to find where devenv is, find the name of the sln file, and know the magic name "ALL_BUILD". Regardless of the workaround it's extra work. It would be nice for the default build to build the default config. | ||||||||
Steps To Reproduce | See description: set CMAKE_CONFIGURATION_TYPES to not have Debug | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Relationships | |
Relationships |
Notes | |
(0030231) David Cole (manager) 2012-08-11 11:09 |
Sending old, never assigned issues to the backlog. (The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...) If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^] It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing. |
(0041799) Kitware Robot (administrator) 2016-06-10 14:28 |
Resolving issue as `moved`. This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2011-02-09 14:06 | Derek Bruening | New Issue | |
2012-08-11 11:09 | David Cole | Status | new => backlog |
2012-08-11 11:09 | David Cole | Note Added: 0030231 | |
2016-06-10 14:28 | Kitware Robot | Note Added: 0041799 | |
2016-06-10 14:28 | Kitware Robot | Status | backlog => resolved |
2016-06-10 14:28 | Kitware Robot | Resolution | open => moved |
2016-06-10 14:28 | Kitware Robot | Assigned To | => Kitware Robot |
2016-06-10 14:31 | Kitware Robot | Status | resolved => closed |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |