* doc/autoconf.texi (Making testsuite Scripts): It is not necessary,
when using Automake, to write a rule to produce atlocal, since it's
an AC_CONFIG_FILES. Mention that atlocal.in needs to be
distributed, not atconfig.in.
Signed-off-by: Benoit Sigoure <tsuna@lrde.epita.fr>
+2007-11-03 Benoit Sigoure <tsuna@lrde.epita.fr>
+
+ Adjust the documentation of autotest WRT atlocal.
+ * doc/autoconf.texi (Making testsuite Scripts): It is not necessary,
+ when using Automake, to write a rule to produce atlocal, since it's
+ an AC_CONFIG_FILES. Mention that atlocal.in needs to be
+ distributed, not atconfig.in.
+
2007-11-04 Eric Blake <ebb9@byu.net>
Update list information.
You might want to list explicitly the dependencies, i.e., the list of
the files @file{testsuite.at} includes.
-With strict Autoconf, you might need to add lines inspired from the
+If you don't use Automake, you might need to add lines inspired from the
following:
@example
@end example
@noindent
-and manage to have @file{atconfig.in} and @code{$(EXTRA_DIST)}
-distributed.
+and manage to have @code{$(EXTRA_DIST)} distributed.
+
+If you use Automake, however, you don't need to add a rule to generate
+@file{atlocal}.
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