Notes
(0019012) David Cole (manager) 2009-12-29 17:22	I am planning to make the following conditions "fatal" errors that halt script processing and exit with informative error messages: - non-existent source directory - source directory exists, but no CMakeLists.txt for a CMake-built project - source directory and CMakeLists.txt exist, but no CTestConfig.cmake with a CTEST_PROJECT_NAME in it... Here are the error messages I am going to use: - for a non-existent source directory CMake Error at quick.cmake:5 (ctest_start): ctest_start given source path C:/Users/.../Dashboards/My Tests/NoSuchDir which is not an existing directory. Set CTEST_CHECKOUT_COMMAND to a command line to create it. Error in read script: C:/Users/.../Dashboards/My Tests/quick.cmake - for a source directory exists, but no CMakeLists.txt for a CMake-built project CMake Error at quick.cmake:8 (ctest_configure): ctest_configure CMakeLists.txt file does not exist 'C:/Users/.../Dashboards/My Tests/playground/Step7/CMakeLists.txt' Error in read script: C:/Users/.../Dashboards/My Tests/quick.cmake - for a source directory and CMakeLists.txt exist, but no CTestConfig.cmake with a CTEST_PROJECT_NAME in it... CMake Error at quick.cmake:10 (ctest_build): ctest_build has no project to build. If this is a "built with CMake" project, verify that CTEST_CMAKE_GENERATOR and CTEST_PROJECT_NAME are set. CTEST_PROJECT_NAME is usually set in CTestConfig.cmake. Verify that CTestConfig.cmake exists, or CTEST_PROJECT_NAME is set in the script, or PROJECT_NAME is passed as an argument to ctest_build. Alternatively, set CTEST_BUILD_COMMAND to build the project with a custom command line. Error in read script: C:/Users/.../Dashboards/My Tests/quick.cmake

(0019013) David Cole (manager) 2009-12-29 18:00	Actually, scratch the "fatal" error part of that last note. For now, I'm just going to improve the error messages so that people encountering them have a shot at figuring out what's wrong just from the text of the error messages. We do not want to induce any fatal errors if it's possible to avoid them: so that the script continues all the way to its bottom line and its ctest_submit call: so that something might show up on the dashboard server even if it's all filled with errors...

(0019014) David Cole (manager) 2009-12-29 18:04	Fixed in CVS HEAD of CMake. Fix for issue 0005041 - improve error messages that may occur during ctest_build and ctest_configure. The improved text gives very clear information when either the CMakeLists.txt or CTestConfig.cmake file is missing. Hopefully, it makes it easier for those poor future souls who encounter these messages to solve their problems quickly. /cvsroot/CMake/CMake/Source/CTest/cmCTestBuildCommand.cxx,v <-- cmCTestBuildCommand.cxx new revision: 1.24; previous revision: 1.23 /cvsroot/CMake/CMake/Source/CTest/cmCTestConfigureCommand.cxx,v <-- cmCTestConfigureCommand.cxx new revision: 1.15; previous revision: 1.14

(0024047) David Cole (manager) 2010-12-14 18:49	Closing bugs that have been resolved for more than 3 months without any further updates.

Issue History
Date Modified	Username	Field	Change
2007-08-31 11:28	Alex Neundorf	Assigned To	System Admin => David Cole
2009-12-29 17:22	David Cole	Note Added: 0019012
2009-12-29 18:00	David Cole	Note Added: 0019013
2009-12-29 18:04	David Cole	Note Added: 0019014
2009-12-29 18:04	David Cole	Status	assigned => resolved
2009-12-29 18:04	David Cole	Resolution	open => fixed
2010-12-14 18:49	David Cole	Note Added: 0024047
2010-12-14 18:49	David Cole	Status	resolved => closed

Relationships