Thanks for the reply, it's clear now. It's also a bit unfortunate though for some cases. The CTEST_TEST(...) call will always result in an exit code of 255 if no tests have been defined in the CMakeLists.txt. Since the script below is called from a build system it would be nice to be able to see if one or more tests failed, or if there were simply no tests defined for that software component (which is not an error).
regards, Arthur On Monday 19 October 2009 20:31:44 David Cole wrote: > The return value of ctest after it runs a -S script indicates whether the > script as a whole succeeded or not. The only way it succeeds all the way and > returns 0 is if *all* of the steps invoked are error free. > The build errors mean that ctest's return value will be non-zero. (Same for > update, configure or test errors as well...) > > > HTH, > David > > > _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
