MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0004615CMakeCMakepublic2007-03-15 21:552016-06-10 14:30
Reporterirwin 
Assigned ToBrad King 
PrioritylowSeveritymajorReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0004615: "test" target should depend on "all" target
DescriptionThe "test" target created by ENABLE_TESTING() should depend on the "all" target since in most cases "make all" has to be run to build the executables used by ctest before ctest can be run using "make test" without giving spurious errors.

I have classified the Severity level as "Significant" since this dependency bug often gives misleading results for "make test" (the ctest invocation shows failed tests, but it takes some digging before you realize it is because the executables required by ctest have not been built).
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-03-27 21:39Bill HoffmanAssigned ToBill Hoffman => Ken Martin
2008-03-28 18:11irwinNote Added: 0010968
2010-12-14 11:20David ColeAssigned ToKen Martin => Brad King
2012-08-13 10:44Brad KingStatusassigned => backlog
2012-08-13 10:44Brad KingNote Added: 0030549
2016-06-10 14:27Kitware RobotNote Added: 0041349
2016-06-10 14:27Kitware RobotStatusbacklog => resolved
2016-06-10 14:27Kitware RobotResolutionopen => moved
2016-06-10 14:30Kitware RobotStatusresolved => closed

Notes
(0010968)
irwin   
2008-03-28 18:11   
After (2008-03-28) discussion on list with Alex Neundorf, I now agree with him that making "test" depend on "all" would add some annoying latency to "make test" (at least for large projects) so a better idea would be to have an option for ADD_TEST to add dependencies for specific targets/files.
(0030549)
Brad King   
2012-08-13 10:44   
Sending issues I'm not actively working on to the backlog to await someone with time for them.

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 or contributor who has the bandwidth to take it on.
(0041349)
Kitware Robot   
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.