MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012539CMake(No Category)public2011-10-26 04:062012-04-02 10:10
ReporterJean-Christophe Fillion-Robin 
Assigned ToDavid Cole 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionCMake 2.8.7Fixed in VersionCMake 2.8.7 
Summary0012539: Expect CTestConfig.cmake in either the build or source directory
DescriptionWould 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.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-10-26 04:06Jean-Christophe Fillion-RobinNew Issue
2011-10-26 04:08Jean-Christophe Fillion-RobinNote Added: 0027653
2011-10-26 04:09Jean-Christophe Fillion-RobinNote Edited: 0027653bug_revision_view_page.php?bugnote_id=27653#r441
2011-10-26 08:11David ColeAssigned To => David Cole
2011-10-26 08:11David ColeStatusnew => assigned
2011-10-26 08:11David ColeTarget Version => CMake 2.8.7
2011-10-26 23:44David ColeNote Added: 0027659
2011-10-26 23:44David ColeStatusassigned => resolved
2011-10-26 23:44David ColeFixed in Version => CMake 2.8.7
2011-10-26 23:44David ColeResolutionopen => fixed
2011-11-21 15:27David ColeNote Added: 0027837
2011-11-21 15:28David ColeNote Edited: 0027837bug_revision_view_page.php?bugnote_id=27837#r457
2012-04-02 10:10David ColeNote Added: 0029048
2012-04-02 10:10David ColeStatusresolved => closed

Notes
(0027653)
Jean-Christophe Fillion-Robin   
2011-10-26 04:08   
(edited on: 2011-10-26 04:09)
From David Cole - Sep 22 2011:

[...]you can override all the settings in CTestConfig already, if you set the variables at the right point in a ctest -S script (typically after the call to ctest_configure...)

That would be an alternative you can consider for using with any ctest 2.8.x
(0027659)
David Cole   
2011-10-26 23:44   
Fix pushed to 'next':

  http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=76ecdd8d169fd2565466669875b5ed7e7c5c1963 [^]
(0027837)
David Cole   
2011-11-21 15:27   
(edited on: 2011-11-21 15:28)
One thing to note about this change, which I just realized after re-reviewing it with another scenario in mind...

Since the code change is in the method:

  bool cmCTest::InitializeFromCommand(cmCTestStartCommand* command)

which is only called from -S scripts that call ctest_start, this technique will only presently work with ctest -S scripts.

In other words, it will NOT work with either "make Experimental" or "ctest -D Experimental" -- for those techniques to work, the information in the (still misnamed) configured file "DartConfiguration.tcl" has to point to the right CDash server... (and possibly also the CTestConfig file in the source tree)
(0029048)
David Cole   
2012-04-02 10:10   
Closing resolved issues that have not been updated in more than 4 months.