From cc647cfe5f492d8810e5b1a6444a37c267c591c4 Mon Sep 17 00:00:00 2001 From: Bill Wendling Date: Fri, 2 Mar 2001 13:14:26 -0500 Subject: [svn-r3537] Purpose: Bug Fix Description: Wasn't building the test programs if user simply did a build with ``make check'' instead of ``make all && make check''. Solution: Put the test programs in the TEST_PROGS macro so that they'd be built. Platforms tested: Linux --- c++/examples/Makefile.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/c++/examples/Makefile.in b/c++/examples/Makefile.in index 2ba0672..67c448a 100644 --- a/c++/examples/Makefile.in +++ b/c++/examples/Makefile.in @@ -27,7 +27,7 @@ TEST_OBJ=$(TEST_SRC:.cpp=.lo) ## These are the programs that `make all' or `make tests' will build and which ## `make check' will run. List them in the order they should be run. -PROGS=$(TEST_SRC:.cpp=) +TEST_PROGS=$(TEST_SRC:.cpp=) TEST_SCRIPTS=$(srcdir)/testexamples.sh @@ -36,7 +36,7 @@ TEST_SCRIPTS=$(srcdir)/testexamples.sh CLEAN= ## How to build the programs... they all depend on the Fortran & C hdf5 libraries -$(PROGS): $(LIB) $(LIBHDF5) +$(TEST_PROGS): $(LIB) $(LIBHDF5) compound: compound.lo @$(LT_LINK_EXE) $(CXXFLAGS) -o $@ compound.lo $(LDFLAGS) $(LIB) $(LIBS) $(LIBHDF5) -- cgit v0.12