Yeah, seems silly, I know. But ctest and cmake both need to know about it, and we didn't (and still don't) want to introduce a dependency of reading the CMakeCache file from ctest.
Let us know if there's still an issue after you do that. On Wed, Oct 3, 2012 at 1:56 PM, Julien Malik <[email protected]> wrote: > OK I did not understand I needed *both*. > Reading the blog article again, I feel stupid. I swear I've read it several > times ;)... > > That must be it. > > Thanks for hint, > Julien > > > Le 03/10/2012 19:25, David Cole a écrit : > >> http://www.kitware.com/blog/home/post/11 >> >> Did you try setting CTEST_USE_LAUNCHERS in the ctest -S script, too? >> >> It's in your CMakeCache already, but it is not set when you run the >> outer level ctest script. The driving ctest needs to know to use >> CTEST_USE_LAUNCHERS also because that's what decides whether to >> generate the Build.xml from the logs of the individually launched >> commands, or whether to scrape the log of the mixed up results of all >> the commands from one giant output stream. >> >> That should fix it. >> >> >> 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
