Hi,
Answering a little bit late: I had a similar problem I wanted to run
only parts of my tests (-R) dedicated test-reports.
As cmake is using absolute paths to the executable the only thing I
needed to copy were the CTestFiles in all sub-directories.
# copy all ctest-files to the current dir
t;> How about
>>
>>
>>
>> cmake --build /my/build/tree --target test
>>
>>
>>
>> Regards,
>>
>> Dvir
>>
>>
>>
>> *From:* CMake [mailto:cmake-boun...@cmake.org] *On Behalf Of *Eric
>> Noulard
>> *Sent:*
How about
cmake --build /my/build/tree --target test
Regards,
Dvir
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Eric Noulard
Sent: Friday, March 24, 2017 13:04
To: CMake Mailinglist <cmake@cmake.org>
Subject: [CMake] Is it possible to run ctest outside build tree?
Is po
gt;
> Dvir
>
>
>
> *From:* CMake [mailto:cmake-boun...@cmake.org] *On Behalf Of *Eric Noulard
> *Sent:* Friday, March 24, 2017 13:04
> *To:* CMake Mailinglist <cmake@cmake.org>
> *Subject:* [CMake] Is it possible to run ctest outside build tree?
>
>
>
>
If the implementation is "run ctest in this build tree" and it
effectively simply does a "pushd $build_tree", runs, and then "popd",
then I don't see why anybody would object to it.
Although, a script wrapper would be completely trivial, and work with
existing ctest.
D
On Fri, Mar 24, 2017
Hi David,
Thank you for you for checking the code. Would you think adding such a
command line option would be acceptable upstream?
Le 24 mars 2017 18:43, "David Cole" a écrit :
This code:
https://github.com/Kitware/CMake/blob/master/Source/ctest.cxx#L139-L157
shows ctest will
This code:
https://github.com/Kitware/CMake/blob/master/Source/ctest.cxx#L139-L157
shows ctest will look for a CTestTestfile.cmake or DartTestfile.txt
file in the current working directory as soon as it starts. Except in
the case of processing a "--launch" directive, in which case, it
dispatches
Is possible to run ctest outside the builld tree and how?
typical use is when I have an out of source build I may be in the source
tree
and want to run tests without manually going to build tree.
i.e. I currently do:
ninja -C /my/build/tree
is there a similar way to do that with ctest (other