MantisBT - CMake
View Issue Details
0012321CMakeCMakepublic2011-07-07 16:162016-06-10 14:31
Chuck 
Kitware Robot 
normalminoralways
closedmoved 
Windows 7Windows7
CMake 2.8.4 
 
0012321: EXCLUDE_FROM_ALL not working with debuging in Visual Studio 2010
The EXCLUDE_FROM_ALL works fine for the ALL_BUILD target and for
targets from top level directories.

The problem is when I hit the debug button (F5)
it seems to build projects in sub dirs.


I've attached a simple project that reproduces the problem on my computer.

If you look at the solution project dependencies for ALL_BUILD,
DUMMY and test_ut are not included.

If you look at the project property -> Configuration -> Debugging -> Configuration Manager
You can see that the top level DUMMY project is not included
but the test_ut project is included as a dependency.

I traced this through to the solution file.
If I remove the Build.0 lines for test_ut:
     {C0BAEDA0-D5C5-4F4B-9ED0-20138A689CAC}.Debug|x64.Build.0 = Debug|x64

From:
GlobalSection(ProjectConfigurationPlatforms) = postSolution

It seems to work like I would expect(like).
No tags attached.
zip test.zip (1,557) 2011-07-07 16:16
https://public.kitware.com/Bug/file/3966/test.zip
Issue History
2011-07-07 16:16ChuckNew Issue
2011-07-07 16:16ChuckFile Added: test.zip
2011-07-07 16:41David ColeAssigned To => David Cole
2011-07-07 16:41David ColeStatusnew => assigned
2012-08-13 15:40David ColeStatusassigned => backlog
2012-08-13 15:40David ColeNote Added: 0030624
2012-11-21 14:51David ColeAssigned ToDavid Cole =>
2012-11-21 14:54David ColeNote Added: 0031646
2016-06-10 14:28Kitware RobotNote Added: 0041858
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
(0030624)
David Cole   
2012-08-13 15:40   
Sending old, not-recently-updated issues to the backlog.

(The age of the bug alone 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.
(0031646)
David Cole   
2012-11-21 14:54   
Un-assigning bugs that are not on the active roadmap, which no developers are actively working on for the CMake 2.8.11 release.

If one gets put back on the roadmap, re-assign it appropriately at that time.
(0041858)
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.