On Mon, 2018-12-31 at 10:48 +1000, Peter Johansson wrote:
> Interesting. I've used this pattern for long time here
>
> https://sourceforge.net/p/yat-util/code/HEAD/tree/trunk/Makefile.am
Thank you Peter. I ended up doing something very similar.
> The most significant difference I can see is
On Sun, 2018-12-30 at 19:19 -0500, Nick Bowler wrote:
> So you just need to change the spelling in the rule, usually by
> using a variable like:
>
> test_stop_log = test-stop.log
> $(test_stop_log): blah blah blah
Thanks Nick. That was very helpful. Basically I just gave all relevant
targets
Hi Kip and Nick,
On 12/30/2018 12:03 PM, Kip Warner wrote:
Almost! The problem is with the last rule you defined because a rule to
generate test-stop.log would have already been generated by Automake
and this would override it. I tested in my own source tree and
confirmed that:
On 12/29/18, Kip Warner wrote:
> On Sat, 2018-12-29 at 16:10 -0500, Nick Bowler wrote:
[...]
>> all_tests_except_start = test1.log test2.log test3.log test-
>> stop.log
>> all_tests_except_stop = test-start.log test1.log test2.log
>> test3.log
>>
>> $(all_tests_except_start): test-start.log
On Sat, 2018-12-29 at 16:10 -0500, Nick Bowler wrote:
> Hello,
Hey Nick,
> OK, I am assuming you are using the Automake parallel-tests feature.
Yes, that's correct.
> So there's no problem with building the programs, the issue is just
> in the execution order of the test cases? You have one
Hello,
On 2018-12-29, Kip Warner wrote:
> Parallel builds work fine for my build tree of a system daemon I am
> developing. I have unit tests in the form of check_SCRIPTS and
> check_PROGRAMS.
>
> These unit tests, however, can only be partially parallelized because
> there needs to be some
Hey list,
Parallel builds work fine for my build tree of a system daemon I am
developing. I have unit tests in the form of check_SCRIPTS and
check_PROGRAMS.
These unit tests, however, can only be partially parallelized because
there needs to be some ordering constraints.
I have a unit test in
