On 2013-01-24 23:07+0100 Wojciech Knapik wrote:
Anyway - yeah, the dependencies are there now and I don't think I'm
missing any. If I create a target foo, that depends on bar and qux and
both bar and qux do target_link_libraries(target fred), then when I try
to build foo in parallel, I get a rac
On Thu, Jan 24, 2013 at 11:19:11AM -0800, Alan W. Irwin wrote:
> Therefore, I advice using unique target names (just like I do). If
> you happen to like a particular target name such as "ut", then append
> a suffix to it (such as subdirectory name) to make that target easy to
> identify and globa
On 2013-01-24 12:26+0100 wmkna...@gmail.com wrote:
Could you describe your approach in more detail ? If I understand it correctly,
it requires quite a bit of manual maintenance...
It does require initial work to set up the dependencies (see below)
properly to avoid race conditions. But there
On 2013-01-23 23:52, Alan W. Irwin wrote:
Whether ordinary or custom targets can be built in parallel depends on
the back-end being used. For the "Unix Makefiles" generator it is
simple;
make -j8 test_everything
With the Ninja generator it is even easier; 'ninja []' :-). (You
can also give -
s way, they'll be able
to build any subtree of tests by simply typing 'make -j'.
Is this a common approach ? How do you guys manage these issues ?
WK
- Reply message -
From: "wmkna...@gmail.com"
To:
Subject: Re: [CMake] Building all tests in parallel (whole subtrees)
ly message -
From: "wmkna...@gmail.com"
To:
Subject: Re: [CMake] Building all tests in parallel (whole subtrees)
Date: Thu, Jan 24, 2013 12:26
Could you describe your approach in more detail ? If I understand it correctly,
it requires quite a bit of manual maintenance...
I've trie
Reply message -
From: "Alan W. Irwin"
To: "Matthew Woehlke"
Cc:
Subject: [CMake] Building all tests in parallel (whole subtrees)
Date: Thu, Jan 24, 2013 05:52
On 2013-01-23 19:07-0500 Matthew Woehlke wrote:
> On 2013-01-23 18:08, Wojciech Knapik wrote:
>> I set up
e] Building all tests in parallel (whole subtrees)
Date: Thu, Jan 24, 2013 01:07
On 2013-01-23 18:08, Wojciech Knapik wrote:
> I set up targets that build the unit test executables and
> marked them with EXCLUDE_FROM_ALL, because I don't want to tie building
> them to building the a
On 24 January 2013 00:07, Matthew Woehlke wrote:
> On 2013-01-23 18:08, Wojciech Knapik wrote:
>
>> I set up targets that build the unit test executables and
>> marked them with EXCLUDE_FROM_ALL, because I don't want to tie building
>> them to building the application code. Now I need a way to bui
2013/1/24 Wojciech Knapik :
> Hello everyone
>
> I'm just about done switching a project from plain makefiles to CMake
> and so far it's been great.
>
> As one of the last steps, I wanted to add support for building/running
> unit tests. I set up targets that build the unit test executables and
> m
On 2013-01-23 19:07-0500 Matthew Woehlke wrote:
On 2013-01-23 18:08, Wojciech Knapik wrote:
I set up targets that build the unit test executables and
marked them with EXCLUDE_FROM_ALL, because I don't want to tie building
them to building the application code. Now I need a way to build and run
On 2013-01-23 18:08, Wojciech Knapik wrote:
I set up targets that build the unit test executables and
marked them with EXCLUDE_FROM_ALL, because I don't want to tie building
them to building the application code. Now I need a way to build and run
these tests en masse, since there are too many to
Hello everyone
I'm just about done switching a project from plain makefiles to CMake
and so far it's been great.
As one of the last steps, I wanted to add support for building/running
unit tests. I set up targets that build the unit test executables and
marked them with EXCLUDE_FROM_ALL, becaus
13 matches
Mail list logo
