View Issue Details [ Jump to Notes ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0005946CMakeCMakepublic2007-10-24 09:192016-06-10 14:30
ReporterOliver Schoen 
Assigned ToBill Hoffman 
PrioritylowSeveritymajorReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0005946: Separation between Debug and Release builds
DescriptionTaking the debug and release separation shown on Visual Studio to would be a good idea to port this to other targets - this could be made dependent to the environment variable DEBUG set or not or any other trigger that does not have an affect to CMakeCache.txt - it is not possible to run a debug and a release build on the same machine and same directory but different debug settings active.
TagsNo tags attached.
Attached Files

 Relationships
child of 0014539closedKitware Robot Multiple output configurations 

  Notes
(0009543)
Oliver Schoen (reporter)
2007-10-24 09:24

 Actually this is a CMAKE issue and not CCMAKE
(0009952)
Bill Hoffman (manager)
2007-12-17 12:11

 I am not sure what you want here?
(0010085)
Oliver Schoen (reporter)
2008-01-07 03:47

 When the MSVC generator creates project files they are mainly split into release and debug build trees and this is very helpful hence the obect files don not interfere with each other.

In the case of the Unix generator it creates a single make structure that cannot have independent debug and release builds.

With some cmake coding I managed to separate the whole cmake build tree but I believe it would be more appropriate to allow this on a more cmake base level without all this logic.

Best Regards,
Oliver
(0010088)
Bill Hoffman (manager)
2008-01-07 08:30

 OK, so you want Debug/Release/etc directories with the makefile generators?
(0010191)
Oliver Schoen (reporter)
2008-01-18 13:00

 Yes it would be useful if you want to have a clean split.
(0011785)
Philip Lowman (developer)
2008-05-09 14:45

 A multi-solution type Makefile generator might be a good idea for CMake in the long-term because it could start to remove the annoying differences people have when they write CMake code that relies on a single-solution generator but then one day discover that it won't work on a multi-solution generator (i.e. CMAKE_BUILD_TYPE).

Also it would make configuration faster for Unix users that consistently need to build multiple solution types (i.e. Debug and Release) because they wouldn't have to rely on a script to configure two separate build trees.
(0041397)
Kitware Robot (administrator)
2016-06-10 14:27

 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.

 Issue History
Date Modified Username Field Change
2007-10-24 09:19 Oliver Schoen New Issue
2007-10-24 09:24 Oliver Schoen Note Added: 0009543
2007-11-19 10:20 Alex Neundorf Category CCMake => CMake
2007-12-17 12:11 Bill Hoffman Note Added: 0009952
2007-12-17 12:11 Bill Hoffman Status new => assigned
2007-12-17 12:11 Bill Hoffman Assigned To => Bill Hoffman
2007-12-18 10:30 Bill Hoffman Status assigned => closed
2007-12-18 10:30 Bill Hoffman Resolution open => unable to reproduce
2008-01-07 03:47 Oliver Schoen Status closed => feedback
2008-01-07 03:47 Oliver Schoen Resolution unable to reproduce => reopened
2008-01-07 03:47 Oliver Schoen Note Added: 0010085
2008-01-07 08:30 Bill Hoffman Note Added: 0010088
2008-01-18 13:00 Oliver Schoen Note Added: 0010191
2008-05-09 14:45 Philip Lowman Note Added: 0011785
2008-10-09 14:55 Bill Hoffman Status feedback => acknowledged
2008-10-09 14:56 Bill Hoffman Priority normal => low
2013-11-02 10:33 Stephen Kelly Relationship added child of 0014539
2016-06-10 14:27 Kitware Robot Note Added: 0041397
2016-06-10 14:27 Kitware Robot Status acknowledged => resolved
2016-06-10 14:27 Kitware Robot Resolution reopened => moved
2016-06-10 14:30 Kitware Robot Status resolved => closed

Copyright © 2000 - 2018 MantisBT Team