Hi Eric,
* Eric Blake wrote on Wed, Apr 19, 2006 at 04:40:39AM CEST:
> According to Ralf Wildenhues on 4/18/2006 11:24 AM:
> > Rerunning the test with
> > make check TESTSUITEFLAGS='-v -d -x 75'
>
> That's the sort of advice I would find useful in the manual. Right now,
> the 'Making testsuite scripts' node mentions how to hook an autotest
> testsuite into your Makefile, but does not give advice on how to document
> to the end user on how to rerun just a particular test. I'm so used to
> automake's TESTS variable, that I did not think to try TESTSUITEFLAGS.
Definitely a good idea.
How about this?
Cheers,
Ralf
* doc/autoconf.texi (Making testsuite Scripts): Add an example
how to use TESTSUITEFLAGS. Suggested by Eric Blake.
Index: doc/autoconf.texi
===================================================================
RCS file: /cvsroot/autoconf/autoconf/doc/autoconf.texi,v
retrieving revision 1.1018
diff -u -r1.1018 autoconf.texi
--- doc/autoconf.texi 20 May 2006 05:39:03 -0000 1.1018
+++ doc/autoconf.texi 22 May 2006 18:50:05 -0000
@@ -17634,6 +17640,14 @@
and manage to have @file{atconfig.in} and @code{$(EXTRA_DIST)}
distributed.
+With all this in place, and if you have not initialized @samp{TESTSUITEFLAGS}
+within your Makefile, you can fine-tune test suite execution with this
variable,
+for example:
+
[EMAIL PROTECTED]
+make check TESTSUITEFLAGS='-v -d -x 75 -k AC_PROG_CC CFLAGS=-g'
[EMAIL PROTECTED] example
+
@c =============================== Frequent Autoconf Questions, with answers
