I am not sure where I found info on this variable, but the ITK/VTK
projects are always a good resource on the latest trends/development
in CMake/CTest/CPack.
Further, for anyone interested, please note the difference in
CTEST_EXTRA_COVERAGE_GLOB, which lists glob expressions as used by
file
BTW In my own project, I am using a bit more old-school approach to
document also CMake code. I wrote a Doxygen filter which transforms
the CMake code into C code which Doxygen can generate an HTML
documentation for. The source of this filter implemented in Python can
be found at
On Tue, Jan 24, 2012 at 2:51 AM, Eric Noulard eric.noul...@gmail.com wrote:
2012/1/24 Rolf Eike Beer e...@sf-mail.de:
Andreas Schuh wrote:
Hi,
Setting CTEST_EXTRA_COVERAGE_GLOB in the CTestCustom.cmake file can be
used to add additional files which shall be included in the coverage
report.
Hi,
Setting CTEST_EXTRA_COVERAGE_GLOB in the CTestCustom.cmake file can be
used to add additional files which shall be included in the coverage
report. This is useful to ensure that files which are not covered by
any test are still reported with 0% line coverage.
I tried using absolute paths in
Andreas Schuh wrote:
Hi,
Setting CTEST_EXTRA_COVERAGE_GLOB in the CTestCustom.cmake file can be
used to add additional files which shall be included in the coverage
report. This is useful to ensure that files which are not covered by
any test are still reported with 0% line coverage.
Oh,
2012/1/24 Rolf Eike Beer e...@sf-mail.de:
Andreas Schuh wrote:
Hi,
Setting CTEST_EXTRA_COVERAGE_GLOB in the CTestCustom.cmake file can be
used to add additional files which shall be included in the coverage
report. This is useful to ensure that files which are not covered by
any test are
