[cmake-developers] [CMake 0012539]: Expect CTestConfig.cmake in either the build or source directory

Mantis Bug Tracker mantis at public.kitware.com
Wed Oct 26 04:06:20 EDT 2011


The following issue has been SUBMITTED. 
====================================================================== 
http://public.kitware.com/Bug/view.php?id=12539 
====================================================================== 
Reported By:                Jean-Christophe Fillion-Robin
Assigned To:                
====================================================================== 
Project:                    CMake
Issue ID:                   12539
Category:                   (No Category)
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2011-10-26 04:06 EDT
Last Modified:              2011-10-26 04:06 EDT
====================================================================== 
Summary:                    Expect CTestConfig.cmake in either the build or
source directory
Description: 
Would it be possible to include the following topic in the release:
 https://github.com/jcfr/CMake/tree/check-ctestconfig-in-builddir

The change is documented and tests have been added:

Expect CTestConfig.cmake in either the build or source directory …

Provide the ability to configure CTest with setting different from the one
available in the source tree by checking first if CTestConfig.cmake
exists in the build tree first.


The motivation is to allow build system checking out external project to
test and/or package them and submit the associated results to a different
dashboard than the one specified (or not) in the source of the external

project.

For example, the build system of Slicer can checkout, build, test
and package what I will  call "extension". These extensions can be developed
by third party who can test and submit to their own dashboard / project.

When checkout by Slicer build system, the default dashboard can be now
overwritten by adding a custom CTestConfig.cmake to the build directory.
And if not overwritten, it would avoid to create CTestConfig.cmake within
the source checkout of the extension.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-10-26 04:06 Jean-Christophe Fillion-RobinNew Issue                         
          
======================================================================




More information about the cmake-developers mailing list