`TESTSUITEFLAGS' rather than `TESTSUITE_FLAGS', like Autoconf.
* HACKING, README, README.alpha: All uses changed.
+2006-08-30 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
+
+ * Makefile.am (check-local, installcheck-local): Use
+ `TESTSUITEFLAGS' rather than `TESTSUITE_FLAGS', like Autoconf.
+ * HACKING, README, README.alpha: All uses changed.
+
2006-08-28 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
* libltdl/argz.c: Use `#ifdef HAVE_CONFIG_H', to facilitate code
=============
* Use
- make check TESTSUITE_FLAGS=-V
+ make check TESTSUITEFLAGS=-V
make check-local
liberally, on as many platforms as you can. Use as many compilers and
linkers you can.
check-local: tests/atconfig $(srcdir)/$(TESTSUITE)
$(CD_TESTDIR); \
CONFIG_SHELL="$(SHELL)" $(SHELL) $$abs_srcdir/$(TESTSUITE) \
- $(TESTS_ENVIRONMENT) $(BUILDCHECK_ENVIRONMENT) $(TESTSUITE_FLAGS)
+ $(TESTS_ENVIRONMENT) $(BUILDCHECK_ENVIRONMENT) $(TESTSUITEFLAGS)
# Run the test suite on the *installed* tree.
installcheck-local:
$(CD_TESTDIR); \
CONFIG_SHELL="$(SHELL)" $(SHELL) $$abs_srcdir/$(TESTSUITE) \
- $(TESTS_ENVIRONMENT) $(INSTALLCHECK_ENVIRONMENT) $(TESTSUITE_FLAGS) \
+ $(TESTS_ENVIRONMENT) $(INSTALLCHECK_ENVIRONMENT) $(TESTSUITEFLAGS) \
AUTOTEST_PATH="$(exec_prefix)/bin"
# We need to remove any file droppings left behind by testsuite
Libtool comes with two integrated sets of tests to check that your build
is sane. You can run both test suites like this:
- make check TESTSUITE_FLAGS=-V
+ make check TESTSUITEFLAGS=-V
make check-local
The tests of the old test suite run in groups in the various demo
do it like this:
make check TESTS='cdemo-static.test cdemo-make.test cdemo-exec.test' \
- TESTSUITE_FLAGS=-V
+ TESTSUITEFLAGS=-V
Providing that you have a FAIL from the most recent group from a
particular demo directory (like the cdemo-static.test group above), you
VERBOSE=yes make check \
TESTS='cdemo-static.test cdemo-make.test cdemo-exec.test' \
- TESTSUITE_FLAGS=-V | tee cdemo-static-group.log
+ TESTSUITEFLAGS=-V | tee cdemo-static-group.log
In order to enable debug shell tracing, use VERBOSE=debug instead of
VERBOSE=yes.
but simple help may also be obtained through
- make check-local TESTSUITE_FLAGS='--help'
+ make check-local TESTSUITEFLAGS='--help'
For verbose output, add the flag `-v', for running only a subset of the
independent tests, merely specify them by number or by keyword, both of
Libtool comes with two integrated sets of tests to check that your build
is sane. You can run both test suites like this:
- make check TESTSUITE_FLAGS=-V
+ make check TESTSUITEFLAGS=-V
make check-local
The tests of the old test suite run in groups in the various demo
do it like this:
make check TESTS='cdemo-static.test cdemo-make.test cdemo-exec.test' \
- TESTSUITE_FLAGS=-V
+ TESTSUITEFLAGS=-V
Providing that you have a FAIL from the most recent group from a
particular demo directory (like the cdemo-static.test group above), you
VERBOSE=yes make check \
TESTS='cdemo-static.test cdemo-make.test cdemo-exec.test' \
- TESTSUITE_FLAGS=-V | tee cdemo-static-group.log
+ TESTSUITEFLAGS=-V | tee cdemo-static-group.log
In order to enable debug shell tracing, use VERBOSE=debug instead of
VERBOSE=yes.
but simple help may also be obtained through
- make check-local TESTSUITE_FLAGS='--help'
+ make check-local TESTSUITEFLAGS='--help'
For verbose output, add the flag `-v', for running only a subset of the
independent tests, merely specify them by number or by keyword, both of