MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0011830CMakeCMakepublic2011-02-09 14:062016-06-10 14:31
ReporterDerek Bruening 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
PlatformIntelOSWindowsOS Version7
Product VersionCMake 2.8.3 
Target VersionFixed in Version 
Summary0011830: cmake --build and ctest_build() assume "Debug" is the default config for multi-config generators
DescriptionIf 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 ReproduceSee description: set CMAKE_CONFIGURATION_TYPES to not have Debug
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-02-09 14:06Derek BrueningNew Issue
2012-08-11 11:09David ColeStatusnew => backlog
2012-08-11 11:09David ColeNote Added: 0030231
2016-06-10 14:28Kitware RobotNote Added: 0041799
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0030231)
David Cole   
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   
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.