[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Introduce TESTSUITE_FLAGS
From: |
Alexandre Duret-Lutz |
Subject: |
Re: Introduce TESTSUITE_FLAGS |
Date: |
Sat, 18 Dec 2004 12:08:27 +0100 |
On Sat, Dec 18, 2004 at 02:09:45AM -0800, Noah Misch wrote:
> I have patched my tests/Makefile.am as follows for the last few weeks, and I
> suspect others may find it handy. This lets me run
>
> make check TESTSUITE_FLAGS="-k autotest"
The GNU convention is to append `FLAGS' to the program's variable.
That would yield `TESTSUITEFLAGS'. (The only exception I know to this
rule is `DISTCHECK_CONFIGURE_FLAGS', and ISTR it's a mistake of mine.)
> --- ac-clean/doc/autoconf.texi 2004-12-15 02:29:03.000000000 -0500
> +++ ac-ts_flags/doc/autoconf.texi 2004-12-18 05:06:03.252195958 -0500
> @@ -15614,10 +15614,14 @@ With Automake, here is a minimal example
> check} with a validation suite.
>
> @example
> -EXTRA_DIST = testsuite.at testsuite
> +EXTRA_DIST = testsuite.at testsuite atlocal.in
> TESTSUITE = $(srcdir)/testsuite
It's not directly related, but maybe you can fix this along the way:
EXTRA_DIST = testsuite.at $(TESTSUITE) atlocal.in
The problem is that as soon as `$(srcdir)/foo' is used in some
dependency or target of a Makefile, it should be spelled this way
everywhere else. Otherwise BSD make gets confused.