2005-02-01 11:17:02 +08:00
|
|
|
#
|
2007-02-08 06:28:58 +08:00
|
|
|
# Copyright by The HDF Group.
|
2005-02-01 11:17:02 +08:00
|
|
|
# Copyright by the Board of Trustees of the University of Illinois.
|
|
|
|
|
# All rights reserved.
|
|
|
|
|
#
|
|
|
|
|
# This file is part of HDF5. The full HDF5 copyright notice, including
|
|
|
|
|
# terms governing use, modification, and redistribution, is contained in
|
2017-04-18 03:32:16 +08:00
|
|
|
# the COPYING file, which can be found at the root of the source code
|
|
|
|
|
# distribution tree, or in https://support.hdfgroup.org/ftp/HDF5/releases.
|
|
|
|
|
# If you do not have access to either file, you may request a copy from
|
|
|
|
|
# help@hdfgroup.org.
|
2005-02-01 11:17:02 +08:00
|
|
|
##
|
|
|
|
|
## Makefile.am
|
|
|
|
|
## Run automake to generate a Makefile.in from this file.
|
|
|
|
|
#
|
|
|
|
|
# HDF5-Fortran test/Makefile(.in)
|
|
|
|
|
#
|
2014-04-06 23:56:21 +08:00
|
|
|
# Autoconf cannot figure out dependencies between modules; disable parallel make
|
|
|
|
|
.NOTPARALLEL:
|
2005-02-01 11:17:02 +08:00
|
|
|
include $(top_srcdir)/config/commence.am
|
|
|
|
|
|
|
|
|
|
# Include files
|
[svn-r17616] Purpose:
CFLAGS overhaul
Description:
Modified the way configure handles CFLAGS.
(note: all changes also apply to FCFLAGS, CXXFLAGS, CPPFLAGS, and LDFLAGS).
1. The configure process will now always preserve a user's CFLAGS
environment variable setup. Any additional flags necessary for compilation
added at configure time will be passed into the Makefiles as AM_CFLAGS,
which is an automake construct to be used in addition to CFLAGS.
This will allow a user to have the final say, as CFLAGS will always appear
later in the compile line than AM_CFLAGS. Additionally, setting CFLAGS
during make will no longer completely erase all flags set by configure,
since they're maintained in AM_CFLAGS.
2. Additionally, where possible, flags previously being assigned directly
into CFLAGS (and thus propagating into h5cc) have now been redirected into
H5_CFLAGS, so they're used ONLY for compiling hdf5, and not embedded into
the h5cc wrapper script as well.
*Note that H5_CFLAGS ultimately is assigned into AM_CFLAGS for use in the
Makefiles. Complete description of changes and build process will be
included in a Configure Document that Elena and I are working on.
3. Removed unsupported config files. This includes:
config/dec-osf*
config/hpux11.00
config/irix5.x
config/powerpc-ibm-aix4.x
config/rs6000-ibm-aix5.x
config/unicos*
4. Modified configure summary to display additional values. Specifically,
appropriate AM_* variables are being shown, as well as H5_FCFLAGS and
H5_CXXFLAGS, which were for some reason not already present.
Tested:
- H5committest
- Tested on all THG / NCSA machines, using several combinations of the more
prominent configure options (c++, fortran, szip, threadsafe, parallel,
et cetera). (Thanks to Quincey for rysnc testing setup!)
- With regards to new automated testing, anything *necessary* for
compilation will be caught by the daily tests as it stands now. (i.e.,
if LDFLAGS is not properly set when szip is used, linking will fail).
Additionally, with regards to which flags get into h5cc, if any
*necessary* flags have been improperly removed, then daily tests should
fail during make installcheck. Additional machine-specific desired
behaviors and/or checks may have to be set up separately within the
daily tests, so this is something to work on.
2009-10-08 23:17:30 +08:00
|
|
|
AM_FCFLAGS+=-I$(top_builddir)/fortran/src $(F9XMODFLAG)$(top_builddir)/fortran/src
|
2014-04-01 01:07:05 +08:00
|
|
|
AM_CPPFLAGS+=-I$(top_srcdir)/src -I$(top_builddir)/fortran/src
|
2005-02-01 11:17:02 +08:00
|
|
|
|
|
|
|
|
# The Fortran test library
|
[svn-r11411] Purpose:
Bug fix
Description:
Building with --disable-static seems to have been broken on several platforms.
Fixed this.
Configure will now disable shared libraries automatically when using pgf90
or when building on Cygwin.
Solution:
To avoid errors when using shared libraries with pgf90 (which I had not
realized were compiler-specific), I had manually set convenience libraries
to use the -static linking flag. Apparently, this is not necessary, and
caused these libraries to be created as empty archives when --disable-static
was used.
Also, some libraries were including other libraries, which was not
necessary.
I also fixed code in configure.in to correctly detect whether shared
or static libraries are enabled, and moved code that disables shared libraries
to before libtool is created (rather than editing libtool after the fact).
Despite repeated warnings that only one shared library can be linked at a
time, I have yet to have shared libraries break the linking of tests on
any system. We'll see if the Daily Tests turn up anything.
Platforms tested:
mir (fortran, C++), sleipnir (C++), modi4 (fortran, C++, parallel),
sol (fortran, C++), cygwin
2005-09-14 06:30:33 +08:00
|
|
|
noinst_LTLIBRARIES=libh5test_fortran.la
|
2005-02-01 11:17:02 +08:00
|
|
|
|
2005-09-16 05:30:06 +08:00
|
|
|
# Some Fortran compilers can't build shared libraries, so sometimes we
|
|
|
|
|
# want to build a shared C library and a static Fortran library. If so,
|
|
|
|
|
# pass the -static flag to the library linker.
|
|
|
|
|
if FORTRAN_SHARED_CONDITIONAL
|
|
|
|
|
else
|
[svn-r17616] Purpose:
CFLAGS overhaul
Description:
Modified the way configure handles CFLAGS.
(note: all changes also apply to FCFLAGS, CXXFLAGS, CPPFLAGS, and LDFLAGS).
1. The configure process will now always preserve a user's CFLAGS
environment variable setup. Any additional flags necessary for compilation
added at configure time will be passed into the Makefiles as AM_CFLAGS,
which is an automake construct to be used in addition to CFLAGS.
This will allow a user to have the final say, as CFLAGS will always appear
later in the compile line than AM_CFLAGS. Additionally, setting CFLAGS
during make will no longer completely erase all flags set by configure,
since they're maintained in AM_CFLAGS.
2. Additionally, where possible, flags previously being assigned directly
into CFLAGS (and thus propagating into h5cc) have now been redirected into
H5_CFLAGS, so they're used ONLY for compiling hdf5, and not embedded into
the h5cc wrapper script as well.
*Note that H5_CFLAGS ultimately is assigned into AM_CFLAGS for use in the
Makefiles. Complete description of changes and build process will be
included in a Configure Document that Elena and I are working on.
3. Removed unsupported config files. This includes:
config/dec-osf*
config/hpux11.00
config/irix5.x
config/powerpc-ibm-aix4.x
config/rs6000-ibm-aix5.x
config/unicos*
4. Modified configure summary to display additional values. Specifically,
appropriate AM_* variables are being shown, as well as H5_FCFLAGS and
H5_CXXFLAGS, which were for some reason not already present.
Tested:
- H5committest
- Tested on all THG / NCSA machines, using several combinations of the more
prominent configure options (c++, fortran, szip, threadsafe, parallel,
et cetera). (Thanks to Quincey for rysnc testing setup!)
- With regards to new automated testing, anything *necessary* for
compilation will be caught by the daily tests as it stands now. (i.e.,
if LDFLAGS is not properly set when szip is used, linking will fail).
Additionally, with regards to which flags get into h5cc, if any
*necessary* flags have been improperly removed, then daily tests should
fail during make installcheck. Additional machine-specific desired
behaviors and/or checks may have to be set up separately within the
daily tests, so this is something to work on.
2009-10-08 23:17:30 +08:00
|
|
|
AM_LDFLAGS+=-static
|
2005-09-16 05:30:06 +08:00
|
|
|
endif
|
|
|
|
|
|
2005-02-01 11:17:02 +08:00
|
|
|
# Our main targets, the tests themselves
|
2019-05-17 04:05:12 +08:00
|
|
|
TEST_PROG=fortranlib_test fflush1 fflush2 fortranlib_test_1_8 fortranlib_test_F03 vol_connector
|
2011-08-18 22:32:47 +08:00
|
|
|
|
2005-02-01 11:17:02 +08:00
|
|
|
check_PROGRAMS=$(TEST_PROG)
|
|
|
|
|
|
2015-08-11 22:35:30 +08:00
|
|
|
libh5test_fortran_la_SOURCES = tf_gen.F90 tf.F90 t.c
|
2005-02-01 11:17:02 +08:00
|
|
|
|
2015-09-01 02:49:17 +08:00
|
|
|
fortranlib_test_SOURCES = tH5F.F90 tH5D.F90 tH5R.F90 tH5S.F90 tH5T.F90 tH5VL.F90 tH5Z.F90 \
|
|
|
|
|
tH5Sselect.F90 tH5P.F90 tH5A.F90 tH5I.F90 tH5G.F90 tH5E.F90 tHDF5.F90 fortranlib_test.F90
|
2008-05-04 07:39:37 +08:00
|
|
|
|
2015-09-01 02:49:17 +08:00
|
|
|
fortranlib_test_1_8_SOURCES = tH5O.F90 tH5A_1_8.F90 tH5G_1_8.F90 tH5MISC_1_8.F90 tHDF5_1_8.F90 \
|
|
|
|
|
fortranlib_test_1_8.F90
|
2011-08-18 22:32:47 +08:00
|
|
|
|
2015-09-01 02:49:17 +08:00
|
|
|
fortranlib_test_F03_SOURCES = tH5E_F03.F90 tH5F_F03.F90 tH5L_F03.F90 \
|
|
|
|
|
tH5O_F03.F90 tH5P_F03.F90 tH5T_F03.F90 tHDF5_F03.F90 fortranlib_test_F03.F90
|
2011-08-18 22:32:47 +08:00
|
|
|
|
2019-06-15 03:30:48 +08:00
|
|
|
vol_connector_SOURCES=vol_connector.F90
|
2011-08-18 22:32:47 +08:00
|
|
|
|
2015-09-01 02:49:17 +08:00
|
|
|
fflush1_SOURCES=fflush1.F90
|
|
|
|
|
fflush2_SOURCES=fflush2.F90
|
2005-02-01 11:17:02 +08:00
|
|
|
|
|
|
|
|
# The tests depend on both fortran libraries and both main libraries.
|
2005-02-04 05:59:40 +08:00
|
|
|
LDADD=libh5test_fortran.la $(LIBH5TEST) $(LIBH5F) $(LIBHDF5)
|
2005-02-01 11:17:02 +08:00
|
|
|
|
|
|
|
|
# Temporary files
|
2014-04-08 00:29:23 +08:00
|
|
|
CHECK_CLEANFILES+=*.h5 *.raw
|
2005-08-03 01:59:03 +08:00
|
|
|
MOSTLYCLEANFILES=*.tmp
|
2005-02-01 11:17:02 +08:00
|
|
|
|
2014-04-08 00:29:23 +08:00
|
|
|
# Fortran module files can have different extensions and different names
|
|
|
|
|
# (e.g., different capitalizations) on different platforms. Write rules
|
|
|
|
|
# for them explicitly rather than trying to teach automake about them.
|
|
|
|
|
# They should be installed as headers and removed during clean.
|
|
|
|
|
maintainer-clean-local: clean-local
|
|
|
|
|
distclean-local: clean-local
|
|
|
|
|
clean-local:
|
|
|
|
|
@if test -n "$(F9XMODEXT)" && test "X$(F9XMODEXT)" != "Xo"; then \
|
2015-08-11 22:35:30 +08:00
|
|
|
$(RM) *.$(F9XMODEXT) tf_gen.F90; \
|
2014-04-08 00:29:23 +08:00
|
|
|
fi
|
|
|
|
|
|
2005-04-26 01:43:58 +08:00
|
|
|
# Mark this directory as part of the Fortran API (this affects output
|
|
|
|
|
# from tests in conclude.am)
|
2008-05-19 13:06:51 +08:00
|
|
|
FORTRAN_API=yes
|
2005-04-26 01:43:58 +08:00
|
|
|
|
2015-08-11 22:35:30 +08:00
|
|
|
# helper program we need to build.
|
|
|
|
|
noinst_PROGRAMS = H5_test_buildiface
|
|
|
|
|
|
|
|
|
|
# H5_test_buildiface.F90 generates all the test APIs that have a KIND type associated
|
|
|
|
|
# with them.
|
|
|
|
|
|
|
|
|
|
tf_gen.F90: H5_test_buildiface$(EXEEXT)
|
|
|
|
|
$(RUNSERIAL) ./H5_test_buildiface$(EXEEXT)
|
|
|
|
|
|
|
|
|
|
# H5_test_buildiface.F90 is included in the distribution, and Automake knows
|
|
|
|
|
# how to compile a fortran program given its sources.
|
|
|
|
|
|
|
|
|
|
H5_test_buildiface_SOURCES = H5_test_buildiface.F90
|
|
|
|
|
|
2016-09-27 00:49:06 +08:00
|
|
|
# The build of the H5_test_buildiface does not depend on any libraries, so set it
|
2015-08-11 22:35:30 +08:00
|
|
|
# to nothing.
|
|
|
|
|
|
2016-09-27 00:49:06 +08:00
|
|
|
H5_test_buildiface_LDADD =
|
|
|
|
|
|
2005-08-05 04:23:25 +08:00
|
|
|
# fflush2 depends on files created by fflush1
|
|
|
|
|
fflush2.chkexe_: fflush1.chkexe_
|
|
|
|
|
|
2008-05-21 23:02:24 +08:00
|
|
|
|
2019-07-17 16:23:44 +08:00
|
|
|
include $(top_srcdir)/config/conclude.am
|
