On 11/20/12 8:44 AM, Neil T. Dantam wrote:
That's the route that GNU coreutils has taken recently; in the unlikely
case perl is absent on the the build system, dummy man-pages are
generated.
This would also not work when cross-compiling, I think, since manpages
would always be regenerated
On 11/20/12 7:16 AM, Bob Friesenhahn wrote:
A good paradigm for non-recursive make is to put Automake include
fragments into each directory which support the files in that
directory. The top Automake.am then includes these fragments. It
would be useful if there was a syntax whereby the
You might write a script that generates both the tests and their
list, and have this list included in the Makefile.am. Automake's
own build system do something similar in its bootstrap.sh script:
With this solution, the user cannot chose at runtime a certain number of
tests he wants to run.
Stefano Lattarini wrote:
First, a smaller nit:
-check-TESTS: $(TESTS)
+AM_RECURSIVE_TARGETS += buildtest runtest
+
+buildtest-TESTS: $(TESTS)
+
+check-TESTS: buildtest-TESTS
+ $(MAKE) $(AM_MAKEFLAGS) runtest-TESTS
+
+runtest-TESTS:
@failed=0; all=0; xfail=0;
On Tue, 20 Nov 2012, Peter Johansson wrote:
Makefile.am [in topdir]. For those fragment files, it would probably be
confusing if paths were inserted into variables. Perhaps one could have a
switch to turn that feature on.
Yes, it would be good to have a syntax which tells Automake to
perform
On 11/20/2012 03:58 PM, Alexis Praga wrote:
You might write a script that generates both the tests and their
list, and have this list included in the Makefile.am. Automake's
own build system do something similar in its bootstrap.sh script:
With this solution, the user cannot chose at
Ha, yes. Simple and elegant.
And we can use regexp for defining TESTS (not directly, but a temporary
variable will work well enough).
Adopted, thanks :)
On Tue, Nov 20, 2012 at 5:06 PM, Stefano Lattarini
stefano.lattar...@gmail.com wrote:
On 11/20/2012 03:58 PM, Alexis Praga wrote:
You
