On 1/3/07, Alexander Neundorf <[EMAIL PROTECTED]> wrote:
Why does the cont. build need a CTestConfig.cmake but the nightly build works ok if the settings are inside the CMakeLists.txt ?
CTestConfig.cmake is used by ctest *before* a configure run during a dashboard execution. This would also work if the variables were set in the driving dashboard script (using those new style, not-yet-documented, CTEST_UPDATE() etc. commands) prior to the point where they are needed. Why do I need two special files for ctest, CTestConfig.cmake and
CTestCustom.cmake ?
They were introduced at different times for different reasons. CTestConfig is used independent of a configure run of cmake... CTestCustom is read during a cmake configure step... HTH, David On 1/3/07, Alexander Neundorf <[EMAIL PROTECTED]> wrote:
Hi, I'm running nightly builds for some months now already, and have therefor created a file CTestCustom.cmake, which contains upper error limit, exclude regexps and other things like this. In the top level CMakeLists.txt I have the settings for NIGHTLY_START_TIME, DROP_METHOD, DROP_SITE, DROP_LOCATION and COMPRESS_SUBMISSION. This works ok for the nightly builds. Now I tried to run a cont. build, and then ctest complained it can't find a CTestConfig.cmake. So the cmake wiki told me to put the mentioned settings in the CTestConfig.cmake, I did this now and it seems to work. Why does the cont. build need a CTestConfig.cmake but the nightly build works ok if the settings are inside the CMakeLists.txt ? Why do I need two special files for ctest, CTestConfig.cmake and CTestCustom.cmake ? Bye Alex -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer _______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
_______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
