diff options
author | James Laird <jlaird@hdfgroup.org> | 2005-04-25 17:43:58 (GMT) |
---|---|---|
committer | James Laird <jlaird@hdfgroup.org> | 2005-04-25 17:43:58 (GMT) |
commit | 1cc3666a270a15783574a2f2a7c6d9bc1209a76b (patch) | |
tree | 3eaf75101a3c2d8d76080efedede016449c700a1 /fortran/test | |
parent | 79460590218b9944523809abf9d84688dca34a2e (diff) | |
download | hdf5-1cc3666a270a15783574a2f2a7c6d9bc1209a76b.zip hdf5-1cc3666a270a15783574a2f2a7c6d9bc1209a76b.tar.gz hdf5-1cc3666a270a15783574a2f2a7c6d9bc1209a76b.tar.bz2 |
[svn-r10656] Purpose:
Output tweak
Description:
Test output in C++ and Fortran directories now puts "C++ API:" or
"Fortran API:" in front of the name of the test being run.
I had overlooked the line of code that caused this to happen.
Solution:
Added HDF_CXX and HDF_FORTRAN variables to C++ and Fortran Makefiles.am.
Platforms tested:
heping (minor change)
Diffstat (limited to 'fortran/test')
-rw-r--r-- | fortran/test/Makefile.am | 4 | ||||
-rw-r--r-- | fortran/test/Makefile.in | 4 |
2 files changed, 8 insertions, 0 deletions
diff --git a/fortran/test/Makefile.am b/fortran/test/Makefile.am index 533458b..8d9419a 100644 --- a/fortran/test/Makefile.am +++ b/fortran/test/Makefile.am @@ -57,6 +57,10 @@ LDADD=libh5test_fortran.la $(LIBH5TEST) $(LIBH5F) $(LIBHDF5) # Temporary files MOSTLYCLEANFILES=*.h5 *.tmp +# Mark this directory as part of the Fortran API (this affects output +# from tests in conclude.am) +HDF_FORTRAN=yes + ## Fortran dependencies must be hardcoded, unfortunately. ##FORTLIBTEST_OBJ= fortranlib_test.lo \ ## tH5F.lo tH5D.lo tH5R.lo tH5S.lo tH5T.lo tH5VL.lo tH5Z.lo \ diff --git a/fortran/test/Makefile.in b/fortran/test/Makefile.in index 447ac46..6f8aae7 100644 --- a/fortran/test/Makefile.in +++ b/fortran/test/Makefile.in @@ -378,6 +378,10 @@ LDADD = libh5test_fortran.la $(LIBH5TEST) $(LIBH5F) $(LIBHDF5) # Temporary files MOSTLYCLEANFILES = *.h5 *.tmp +# Mark this directory as part of the Fortran API (this affects output +# from tests in conclude.am) +HDF_FORTRAN = yes + # Automake needs to be taught how to build lib, progs, and tests targets. # These will be filled in automatically for the most part (e.g., # lib_LIBRARIES are built for lib target), but EXTRA_LIB, EXTRA_PROG, and |