MantisBT - CMake
View Issue Details
0012910CMakeCTestpublic2012-01-24 00:522016-06-10 14:31
Andreas Schuh 
Kitware Robot 
normalminoralways
closedmoved 
Apple MacOS X10.4.10
CMake 2.8.7 
 
0012910: FindUncoveredFiles(): Uncovered files only searched in source tree
The cmCTestCoverageHandler::FindUncoveredFiles() method prepends the top directory of the source tree to the glob expressions specified by CTEST_EXTRA_COVERAGE_GLOB in, for example, the CTestCustom.cmake file.

Now is it, however, also common that source files are configured during the configuration of the build system and the configured files are placed in the binary directory. These configured files are the ones which get compiled and linked into the binaries which are executed during testing. For example, consider a config.cxx.in file in the source tree, which is configured to config.cxx in the build tree. When defining extra coverage globs, the file would need to be searched for in the binary tree instead of the source tree.

The FindUncoveredFiles() method should therefore either for each glob expression prepend once the top directory of the source tree and once the top directory of the binary tree or leave absolute glob expression, i.e., ones starting with a leading slash (/) unmodified. If a file is found in both trees, the one in the binary directory should probably take precedence as there must have been a reason that this file was configured/copied to the binary tree.
No tags attached.
Issue History
2012-01-24 00:52Andreas SchuhNew Issue
2012-08-11 21:09David ColeStatusnew => backlog
2012-08-11 21:09David ColeNote Added: 0030355
2016-06-10 14:28Kitware RobotNote Added: 0041971
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
(0030355)
David Cole   
2012-08-11 21: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.
(0041971)
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.