CMake/Tests/CTestTestConfigFileInBuildDir/CTestConfig.cmake

set(CTEST_PROJECT_NAME "CTestTestConfigFileInBuildDir")
set(CTEST_NIGHTLY_START_TIME "01:00:00 UTC")
set(CTEST_DART_SERVER_VERSION "2")
set(CTEST_DROP_METHOD "http")
set(CTEST_DROP_SITE "open.cdash.org")
set(CTEST_DROP_LOCATION "/submit.php?project=PublicDashboard")
set(CTEST_DROP_SITE_CDASH TRUE)
CTest: Look for CTestConfig.cmake in build dir first, then source dir Provide the ability to configure CTest with settings different from the ones available in the source tree by checking first if CTestConfig.cmake exists in the build tree. 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 "extensions". These extensions can be developed by third parties who can test and submit to their own dashboard / project. When checked out by Slicer build system, the default dashboard can now be 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. 2011-10-26 22:48:36 -04:00			`set(CTEST_PROJECT_NAME "CTestTestConfigFileInBuildDir")`
			`set(CTEST_NIGHTLY_START_TIME "01:00:00 UTC")`
			`set(CTEST_DART_SERVER_VERSION "2")`
			`set(CTEST_DROP_METHOD "http")`
Update CDash server URL It is now at open.cdash.org and does not start in "/CDash". 2014-06-24 13:35:33 -04:00			`set(CTEST_DROP_SITE "open.cdash.org")`
			`set(CTEST_DROP_LOCATION "/submit.php?project=PublicDashboard")`
CTest: Look for CTestConfig.cmake in build dir first, then source dir Provide the ability to configure CTest with settings different from the ones available in the source tree by checking first if CTestConfig.cmake exists in the build tree. 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 "extensions". These extensions can be developed by third parties who can test and submit to their own dashboard / project. When checked out by Slicer build system, the default dashboard can now be 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. 2011-10-26 22:48:36 -04:00			`set(CTEST_DROP_SITE_CDASH TRUE)`