[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: proposed patch: parallel-tests: per-extension test driver: ext_COMPI
From: |
Ralf Wildenhues |
Subject: |
Re: proposed patch: parallel-tests: per-extension test driver: ext_COMPILE. |
Date: |
Mon, 30 Mar 2009 21:37:29 +0200 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
* Akim Demaille wrote on Mon, Mar 30, 2009 at 09:25:30PM CEST:
> Le 24 mars 09 à 22:57, Ralf Wildenhues a écrit :
>> How about this? I really appreciate a look over this.
>
> I really appreciate your work :)
Thanks!
>> Note that for extension .foo, the variable names will be FOO_LOG_*,
>> i.e., remove the dot, then uppercase the rest.
>>
>> I chose to go all the way and add AM_*FLAGS too.
>>
>> One could, as a generalization, even add, for the non-extension rules,
>> add
>> LOG_COMPILER = $(LOG_COMPILE) $(AM_LOG_FLAGS) $(LOG_FLAGS)
>
> I think you meant
>
> LOG_COMPILE = $(LOG_COMPILER) $(AM_LOG_FLAGS) $(LOG_FLAGS)
Yes, thanks.
> But what is a non-extension rule? You mean if the rule is
>
> foo: ...
>
> ?
I mean with
TESTS = foo bar.test baz.chk
TEST_EXTENSIONS = .chk
then foo.log and bar.test.log (sic!) will be generated using explicit
rules, while baz.log will be generated using a .chk.log suffix rule.
Only the latter one will have a $(CHK_LOG_COMPILE), while there will be
no $(TEST_LOG_COMPILE) (because .test was not listed as extension), nor
$(LOG_COMPILE) (because foo has no extension). The above proposal was
meant as: adding $(LOG_COMPILE) (as defined above) to those test runs
which are generated by means of explicit rules.
Makes sense now?
Cheers,
Ralf
- proposed patch: parallel-tests: also record logs of SKIPped tests., (continued)
proposed patch: parallel-tests: per-extension test driver: ext_COMPILE., Ralf Wildenhues, 2009/03/14
parallel-tests: do not mark check-TESTS as `.MAKE'., Ralf Wildenhues, 2009/03/28