In my cmake project, there are some subdirectories within it, and some of them
have to build as completed
static or shared libraries.
1. The top project is executable
2. a subdirectory is a shared project, which also have some subdirectoy compile
as static libraries which
of course should ON
Here's a bash script wrapper you could use with existing ctest. Save
it out to a file named ctest-two-labels.sh and then call it with bash
on Mac or Linux:
label1=$1
label2=$2
if [ -z "$label1" ]; then
echo "script takes two label arguments as input, missing arg 1"
exit 1
fi
if [ -z "$l
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 at
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 look for a CTestT
I am proud to announce the third CMake 3.8 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.8
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.8/release/3.8.html
Some of the more significant ch
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
I agree and not at the same time. CMake Tools is an awesome extension, but C++
development in VS Code still feel second rate due to the fact, that the C++
language services extension (most notably the Microsoft extension) does not
know about CMake Tools and one manually has to populate CppSettin
On 03/24/2017 02:04 PM, Eric Noulard wrote:
Is there any plan to create/support a VS Code
(https://code.visualstudio.com/) generator?
Since Visual Studio Code seems to be able to open Visual Studio
Solution is it possible to have a working Visual Studio Generator on
Linux?
Any information/
Is there any plan to create/support a VS Code (
https://code.visualstudio.com/) generator?
Since Visual Studio Code seems to be able to open Visual Studio Solution is
it possible to have a working Visual Studio Generator on Linux?
Any information/experience about using VS Code with CMake on Linux
2017-03-24 12:30 GMT+01:00 Nils Gladitz :
> On 03/24/2017 11:50 AM, Eric Noulard wrote:
>
> Hi there,
>>
>> I'm playing with ctest LABELS and I wanted to know whether if it is
>> possible
>> to run the set of tests which have 2 labels ?
>>
>> I manage to have all tests which have **either** L1 or
On 03/24/2017 11:50 AM, Eric Noulard wrote:
Hi there,
I'm playing with ctest LABELS and I wanted to know whether if it is
possible
to run the set of tests which have 2 labels ?
I manage to have all tests which have **either** L1 or L2:
ctest -L "L1|L2"
but how can I write a proper command
Hi there,
I'm playing with ctest LABELS and I wanted to know whether if it is possible
to run the set of tests which have 2 labels ?
I manage to have all tests which have **either** L1 or L2:
ctest -L "L1|L2"
but how can I write a proper command line for both L1 and L2 ?
apparently
ctest -L "
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 tha
13 matches
Mail list logo
