Re: proposed patch: parallel-tests: per-extension test driver: ext_COMPILE.

2009-04-04 Thread Ralf Wildenhues
* Ralf Wildenhues wrote on Sat, Apr 04, 2009 at 12:16:32PM CEST: > + - In 1.10b, the `parallel-tests' driver introduced per-extension test > +driver variables `_LOG_COMPILER', defined as > + > + $(_LOG_COMPILE) $(AM__LOG_FLAGS) $(_LOG_FLAGS) > + > +for extensions `.ext' registered in

Re: proposed patch: parallel-tests: per-extension test driver: ext_COMPILE.

2009-04-04 Thread Ralf Wildenhues
* Akim Demaille wrote on Mon, Mar 30, 2009 at 10:02:51PM CEST: > Le 30 mars 09 à 21:37, Ralf Wildenhues a écrit : >> 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 ge

Re: proposed patch: parallel-tests: per-extension test driver: ext_COMPILE.

2009-03-30 Thread Akim Demaille
Le 30 mars 09 à 21:37, Ralf Wildenhues a écrit : 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 b

Re: proposed patch: parallel-tests: per-extension test driver: ext_COMPILE.

2009-03-30 Thread Ralf Wildenhues
* 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.,

Re: proposed patch: parallel-tests: per-extension test driver: ext_COMPILE.

2009-03-30 Thread Akim Demaille
Le 24 mars 09 à 22:57, Ralf Wildenhues a écrit : Hi Akim, Hi Ralf! * Akim Demaille wrote on Sat, Mar 14, 2009 at 01:52:33PM CET: Le 14 mars 09 à 12:08, Ralf Wildenhues a écrit : Corollary: the test driver may not be called CXXCOMPILE. General: For extension `.ext', we cannot use `EXTCOM

Re: proposed patch: parallel-tests: per-extension test driver: ext_COMPILE.

2009-03-28 Thread Ralf Wildenhues
* Ralf Wildenhues wrote on Tue, Mar 24, 2009 at 10:57:16PM CET: > How about this? I really appreciate a look over this. > > 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. >

Re: proposed patch: parallel-tests: per-extension test driver: ext_COMPILE.

2009-03-24 Thread Ralf Wildenhues
Hi Akim, * Akim Demaille wrote on Sat, Mar 14, 2009 at 01:52:33PM CET: > Le 14 mars 09 à 12:08, Ralf Wildenhues a écrit : > >> Corollary: the test driver may not be called CXXCOMPILE. General: >> For extension `.ext', we cannot use `EXTCOMPILE' as driver. >> ext_COMPILE or >> extCOMPILE >> >> s

Re: proposed patch: parallel-tests: per-extension test driver: ext_COMPILE.

2009-03-14 Thread Akim Demaille
Le 14 mars 09 à 12:08, Ralf Wildenhues a écrit : Corollary: the test driver may not be called CXXCOMPILE. General: For extension `.ext', we cannot use `EXTCOMPILE' as driver. ext_COMPILE or extCOMPILE seem awkward to me too, as these do not allow for generalization either, and the notationa

proposed patch: parallel-tests: per-extension test driver: ext_COMPILE.

2009-03-14 Thread Ralf Wildenhues
This needs some thinking about the naming scheme to use. Here's why: The current Automake default compile naming scheme has the assumption that file extensions have only one default processing output. For example, .c and .cpp become .$(OBJEXT), .y become .c, and so on. Texinfo is an exception, b