> > You can do it all in one step with ctest, but you have to write a > ctest -S script, and call that... Inside it, you can do a "configure > from scratch" using the ctest_configure(...) command. Then you'll see > all the configure output submitted to the dashboard. > > Poke around the wiki and the mailing list for ctest -S script > documentation. (Go with a new style script that uses the commands > 'ctest_configure' and 'ctest_build' and 'ctest_test'.) Maybe somebody > else has time to chime in and give you more details. > > > Cheers, > David >
Thanks fot hints - I finally managed to make it work using ctest scripting. Basic setup was quite easy, but for a longer while I coudn't find a way to have the BuildName and Site name being set - instead they were void. This resulted in having separate entries being shown in CDash for all three stages: configure, build and test. As suggested by wiki entries I tried playing with setting initial cache but it did not work. After few hours I found out that I need to set variables CTEST_BUILD_NAME and CTEST_SITE in the CTestConfig.cmake file. Once I did that the CDash entries were non-void and the submissions were merged together. With CTest -S working now I have a system with subprojects, and with labels not assigned as subprojects as well, what by the means of filtering feature gives me a very nice possibility to browse submissions by labels, something I asked about in one of my recent posts. Thanks, Wojtek ---------------------------------------------------------------------- Szukasz pracy? Możemy Ci ją dać! Sprawdź >> http://linkint.pl/f288d _______________________________________________ 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
