[CMake] Random behavior of CTEST_USE_LAUNCHERS

Julien Malik julien.malik at c-s.fr
Thu Oct 4 03:38:28 EDT 2012


Hi David,

That was it.
You make my day!

Thanks,
Julien


Le 03/10/2012 20:24, David Cole a écrit :
> 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 <julien.malik at c-s.fr> 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
>>>



More information about the CMake mailing list