David Cole wrote: > On Fri, Dec 11, 2009 at 3:58 AM, Martin Apel <[email protected] > <mailto:[email protected]>> wrote: > > Hi all, > > I tried to set some CTest custom variables such as > CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE in the CTestCustom.cmake > file in the binary directory. > This works as long as I run ctest interactively, e.g. "ctest -D > Experimental". In this case, the test output is not cut off. If I > do the > same using a CTest script, it seems the CTestCustom.cmake file > is completely ignored, so the test output is cut off at the default > value of 1024 characters. > Is this intended behaviour or is it a bug? > > > Probably a little bit of each... > > Try putting a call to: > CTEST_READ_CUSTOM_FILES("${CTEST_BINARY_DIRECTORY}") > > after ctest_configure and before ctest_build... > > One could certainly make the argument that this should be entirely > invisible and automatic and buried inside the ctest_configure call. In > that sense, it's a bug. > > I know the author of the ctest_read_custom_files command intended > things to be this way, but I still do not understand why... Perhaps if > nobody can explain why it should be left this way, it would make sense > to try to make this implied/automatic at the end of a ctest_configure > command.... > > > HTH, > David Hi David,
thanks a lot, this did the trick. Regards, Martin
_______________________________________________ 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
