libtool-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

TESTSUITE_FLAGS -> TESTSUITEFLAGS


From: Ralf Wildenhues
Subject: TESTSUITE_FLAGS -> TESTSUITEFLAGS
Date: Tue, 29 Aug 2006 20:38:46 +0200
User-agent: Mutt/1.5.13 (2006-08-11)

Autoconf uses TESTSUITEFLAGS and also documents this in its example
setup, and I get confused when switching back and forth.  OK to apply?

Cheers,
Ralf

        * Makefile.am (check-local, installcheck-local): Use
        `TESTSUITEFLAGS' rather than `TESTSUITE_FLAGS', like Autoconf.
        * HACKING, README, README.alpha: All uses changed.

Index: HACKING
===================================================================
RCS file: /cvsroot/libtool/libtool/HACKING,v
retrieving revision 1.29
diff -u -r1.29 HACKING
--- HACKING     28 Aug 2006 16:02:14 -0000      1.29
+++ HACKING     29 Aug 2006 16:46:21 -0000
@@ -52,7 +52,7 @@
 =============
 
 * 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.
Index: Makefile.am
===================================================================
RCS file: /cvsroot/libtool/libtool/Makefile.am,v
retrieving revision 1.196
diff -u -r1.196 Makefile.am
--- Makefile.am 10 Jun 2006 07:36:25 -0000      1.196
+++ Makefile.am 29 Aug 2006 16:46:21 -0000
@@ -468,13 +468,13 @@
 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
Index: README
===================================================================
RCS file: /cvsroot/libtool/libtool/README,v
retrieving revision 1.25
diff -u -r1.25 README
--- README      30 Jan 2006 20:09:41 -0000      1.25
+++ README      29 Aug 2006 16:46:21 -0000
@@ -41,7 +41,7 @@
 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
@@ -56,7 +56,7 @@
 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
@@ -71,7 +71,7 @@
 
   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.
@@ -84,7 +84,7 @@
 
 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
Index: README.alpha
===================================================================
RCS file: /cvsroot/libtool/libtool/README.alpha,v
retrieving revision 1.9
diff -u -r1.9 README.alpha
--- README.alpha        30 Jan 2006 20:09:41 -0000      1.9
+++ README.alpha        29 Aug 2006 16:46:21 -0000
@@ -44,7 +44,7 @@
 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
@@ -59,7 +59,7 @@
 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
@@ -74,7 +74,7 @@
 
   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.
@@ -87,7 +87,7 @@
 
 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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]