2005-02-12 01:40:52 +08:00
|
|
|
## config/commence.am
|
2007-02-21 23:43:35 +08:00
|
|
|
## (Use double hashes for copyright notice so that automake treats it as
|
|
|
|
|
## comments and does not pass it to Makefile.in)
|
|
|
|
|
## Copyright by The HDF Group.
|
|
|
|
|
## Copyright by the Board of Trustees of the University of Illinois.
|
|
|
|
|
## All rights reserved.
|
2005-10-21 22:54:41 +08:00
|
|
|
##
|
2007-02-21 23:43:35 +08:00
|
|
|
## 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
|
2021-02-17 22:52:36 +08:00
|
|
|
## distribution tree, or in https://www.hdfgroup.org/licenses.
|
2017-04-18 03:32:16 +08:00
|
|
|
## If you do not have access to either file, you may request a copy from
|
|
|
|
|
## help@hdfgroup.org.
|
2005-10-21 22:54:41 +08:00
|
|
|
|
|
|
|
|
|
2005-02-12 01:40:52 +08:00
|
|
|
## Textually included in the beginning of every HDF5 Makefile.am
|
|
|
|
|
## Contains definitions, etc. used across multiple Makefiles.
|
2005-02-01 11:17:02 +08:00
|
|
|
|
|
|
|
|
# Shell commands used in Makefiles
|
|
|
|
|
RM=rm -f
|
|
|
|
|
CP=cp
|
|
|
|
|
|
2005-04-01 02:26:17 +08:00
|
|
|
# Some machines need a command to run executables; this is that command
|
|
|
|
|
# so that our tests will run.
|
2010-01-13 07:58:30 +08:00
|
|
|
# We use RUNEXEC instead of RUNSERIAL directly because it may be that
|
2005-04-01 02:26:17 +08:00
|
|
|
# some tests need to be run with a different command. Older versions
|
|
|
|
|
# of the makefiles used the command
|
|
|
|
|
# $(LIBTOOL) --mode=execute
|
|
|
|
|
# in some directories, for instance.
|
2010-01-13 07:58:30 +08:00
|
|
|
RUNEXEC=$(RUNSERIAL)
|
2005-04-01 02:26:17 +08:00
|
|
|
|
2005-02-01 11:17:02 +08:00
|
|
|
# Libraries to link to while building
|
|
|
|
|
LIBHDF5=$(top_builddir)/src/libhdf5.la
|
|
|
|
|
LIBH5TEST=$(top_builddir)/test/libh5test.la
|
|
|
|
|
LIBH5F=$(top_builddir)/fortran/src/libhdf5_fortran.la
|
|
|
|
|
LIBH5FTEST=$(top_builddir)/fortran/test/libh5test_fortran.la
|
|
|
|
|
LIBH5CPP=$(top_builddir)/c++/src/libhdf5_cpp.la
|
2016-02-29 10:43:00 +08:00
|
|
|
LIBH5JNI=$(top_builddir)/java/src/jni/libhdf5_java.la
|
2005-02-01 11:17:02 +08:00
|
|
|
LIBH5TOOLS=$(top_builddir)/tools/lib/libh5tools.la
|
|
|
|
|
LIBH5_HL=$(top_builddir)/hl/src/libhdf5_hl.la
|
|
|
|
|
LIBH5F_HL=$(top_builddir)/hl/fortran/src/libhdf5hl_fortran.la
|
2005-03-29 00:32:20 +08:00
|
|
|
LIBH5CPP_HL=$(top_builddir)/hl/c++/src/libhdf5_hl_cpp.la
|
2005-02-01 11:17:02 +08:00
|
|
|
|
|
|
|
|
# Install directories that automake doesn't know about
|
|
|
|
|
docdir = $(exec_prefix)/doc
|
|
|
|
|
|
2020-04-21 07:12:00 +08:00
|
|
|
# Note that in svn revision 19400 the '/' after DESTDIR in H5* variables below
|
|
|
|
|
# has been removed. According to the official description of DESTDIR by Gnu at
|
|
|
|
|
# http://www.gnu.org/prep/standards/html_node/DESTDIR.html, DESTDIR is
|
|
|
|
|
# prepended to the normal and complete install path that it precedes for the
|
|
|
|
|
# purpose of installing in a temporary directory which is useful for building
|
|
|
|
|
# rpms and other packages. The '/' after ${DESTDIR} will be followed by another
|
|
|
|
|
# '/' at the beginning of the normal install path. When DESTDIR is empty the
|
|
|
|
|
# path then begins with '//', which is incorrect and causes problems at least for
|
|
|
|
|
# Cygwin.
|
2010-10-05 01:15:30 +08:00
|
|
|
|
2005-02-01 11:17:02 +08:00
|
|
|
# Scripts used to build examples
|
[svn-r11646] Purpose:
Bug fix/feature
Description:
Added support for -shlib in h5fc and h5c++.
Made check-install use -shlib when only shared libraries have been installed.
Solution:
h5fc and h5c++ didn't recognize -shlib. Stole code from h5cc to link against
shared libraries.
When static libraries are disabled, the examples Makefiles will automatically
use the -shlib option to link against shared libraries. Thus,
--disable-static and make check-install should work together.
Platforms tested:
heping(disable-static, enable-static, fortran, c++), modi4 (disable-static, fortran, c++, parallel, enable-static)
2005-11-01 05:35:49 +08:00
|
|
|
# If only shared libraries have been installed, have h5cc build examples with
|
|
|
|
|
# shared libraries instead of static libraries
|
2010-10-05 01:15:30 +08:00
|
|
|
H5CC=${DESTDIR}$(bindir)/h5cc
|
|
|
|
|
H5CC_PP=${DESTDIR}$(bindir)/h5pcc
|
|
|
|
|
H5FC=${DESTDIR}$(bindir)/h5fc
|
|
|
|
|
H5FC_PP=${DESTDIR}$(bindir)/h5pfc
|
|
|
|
|
H5CPP=${DESTDIR}$(bindir)/h5c++
|
2020-04-21 07:12:00 +08:00
|
|
|
|
2005-02-01 11:17:02 +08:00
|
|
|
|
[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
|
|
|
# H5_CFLAGS holds flags that should be used when building hdf5,
|
|
|
|
|
# but which should not be exported to h5cc for building other programs.
|
2020-04-21 07:12:00 +08:00
|
|
|
# AM_CFLAGS is an automake construct which should be used by Makefiles
|
[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
|
|
|
# instead of CFLAGS, as CFLAGS is reserved solely for the user to define.
|
2011-04-15 05:21:59 +08:00
|
|
|
# This applies to FCFLAGS, CXXFLAGS, CPPFLAGS, and LDFLAGS as well.
|
2006-06-22 07:15:08 +08:00
|
|
|
|
2020-11-25 11:57:48 +08:00
|
|
|
AM_CFLAGS=@AM_CFLAGS@ @H5_CFLAGS@
|
[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=@AM_FCFLAGS@ @H5_FCFLAGS@
|
2020-11-25 11:57:48 +08:00
|
|
|
AM_CXXFLAGS=@AM_CXXFLAGS@ @H5_CXXFLAGS@
|
[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_CPPFLAGS=@AM_CPPFLAGS@ @H5_CPPFLAGS@
|
2011-04-15 05:21:59 +08:00
|
|
|
AM_LDFLAGS=@AM_LDFLAGS@ @H5_LDFLAGS@
|
2005-09-17 05:26:17 +08:00
|
|
|
|
2010-09-10 23:45:07 +08:00
|
|
|
ACLOCAL_AMFLAGS="-I m4"
|
|
|
|
|
|
2005-11-18 23:55:22 +08:00
|
|
|
# The trace script; this is used on source files from the C library to
|
|
|
|
|
# insert tracing macros.
|
|
|
|
|
TRACE=perl $(top_srcdir)/bin/trace
|
|
|
|
|
|
2005-02-01 11:17:02 +08:00
|
|
|
# Make sure that these variables are exported to the Makefiles
|
|
|
|
|
F9XMODEXT=@F9XMODEXT@
|
2005-02-01 23:27:37 +08:00
|
|
|
F9XMODFLAG=@F9XMODFLAG@
|
2005-02-01 11:17:02 +08:00
|
|
|
|
2005-08-27 06:24:27 +08:00
|
|
|
# .chkexe files are used to mark tests that have run successfully.
|
|
|
|
|
# .chklog files are output from those tests.
|
2015-02-26 02:48:31 +08:00
|
|
|
# *.clog and *.clog2 are from the MPE option.
|
|
|
|
|
CHECK_CLEANFILES=*.chkexe *.chklog *.clog *.clog2
|
2005-08-02 06:22:55 +08:00
|
|
|
|
[svn-r11737] Purpose:
Bug fix
Description:
Before this checkin, 'gmake check-s' would fail if there was a file in
the current directory named 'check-s'.
This is fixed under gmake (not sure how to fix for other makes).
Solution:
check, progs, install, etc. are what gmake calls "phony" targets,
which means that no file should be created. These targets can be
specified by a line of the form
.PHONY: check progs install ...
Automake adds this line for targets it knows about, but HDF5 has a
lot of custom rules. This checkin adds a .PHONY line for those rules.
I believe that only gmake recognizes the .PHONY line (at least, pmake
doesn't seem to), but a partial solution is better than none.
This error should occur very rarely anyway (the user has to manually
create files with names like 'build-check-s' or '_test').
Platforms tested:
mir, sleipnir, modi4
2005-11-18 02:49:28 +08:00
|
|
|
# List all build rules defined by HDF5 Makefiles as "PHONY" targets here.
|
|
|
|
|
# This tells the Makefiles that these targets are not files to be built but
|
|
|
|
|
# commands that should be executed even if a file with the same name already
|
|
|
|
|
# exists.
|
|
|
|
|
.PHONY: build-check-clean build-check-p build-check-s build-lib build-progs \
|
2020-11-04 07:16:00 +08:00
|
|
|
build-tests check-clean check-install check-p check-s check-vfd \
|
|
|
|
|
check-passthrough-vol install-doc lib progs tests uninstall-doc \
|
|
|
|
|
_exec_check-s _test help trace doxygen
|
2007-02-24 03:14:11 +08:00
|
|
|
|
|
|
|
|
help:
|
2020-11-04 07:16:00 +08:00
|
|
|
@$(top_srcdir)/bin/makehelp
|
[svn-r11737] Purpose:
Bug fix
Description:
Before this checkin, 'gmake check-s' would fail if there was a file in
the current directory named 'check-s'.
This is fixed under gmake (not sure how to fix for other makes).
Solution:
check, progs, install, etc. are what gmake calls "phony" targets,
which means that no file should be created. These targets can be
specified by a line of the form
.PHONY: check progs install ...
Automake adds this line for targets it knows about, but HDF5 has a
lot of custom rules. This checkin adds a .PHONY line for those rules.
I believe that only gmake recognizes the .PHONY line (at least, pmake
doesn't seem to), but a partial solution is better than none.
This error should occur very rarely anyway (the user has to manually
create files with names like 'build-check-s' or '_test').
Platforms tested:
mir, sleipnir, modi4
2005-11-18 02:49:28 +08:00
|
|
|
|
