From: Ralf Wildenhues Date: Thu, 25 May 2006 07:39:57 +0000 (+0000) Subject: * doc/autoconf.texi (Making testsuite Scripts): Add an example X-Git-Tag: AUTOCONF-2.59d~45 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=4814eec7e01ae013fecbfc33273b96161c51c957;p=thirdparty%2Fautoconf.git * doc/autoconf.texi (Making testsuite Scripts): Add an example how to use TESTSUITEFLAGS. Suggested by Eric Blake. --- diff --git a/ChangeLog b/ChangeLog index 4a90155f2..d0a5b66a0 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2006-05-25 Ralf Wildenhues + + * doc/autoconf.texi (Making testsuite Scripts): Add an example + how to use TESTSUITEFLAGS. Suggested by Eric Blake. + 2006-05-24 Ralf Wildenhues * tests/autotest.at (Multiline command from M4 expansion): diff --git a/doc/autoconf.texi b/doc/autoconf.texi index 1c94056c9..34d19df15 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi @@ -17644,6 +17644,14 @@ atlocal: $(srcdir)/atlocal.in $(top_builddir)/config.status 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: + +@example +make check TESTSUITEFLAGS='-v -d -x 75 -k AC_PROG_CC CFLAGS=-g' +@end example + @c =============================== Frequent Autoconf Questions, with answers