How to build HDF-EOS

This page explains how to build the HDF-EOS2 library and the HDF-EOS5 library.

HDF-EOS2

You can get the latest release from here. As of July 2009, HDF-EOS 2.16 v1.00 is the latest version, and you can get the library from their ftp site. There are two tar files for UNIX; one contains source code and sample code, and the other contains code for test drivers.

Because HDF-EOS2 is built on HDF4 , the HDF4 library is required to build the HDF-EOS2 library. HDF4 can optionally be built with the SZIP compression library. If SZIP was used, you need to know the library path. Due to the license issue, there are two types of SZIP libraries: decoder only and encoder/decoder. You need to know which type of SZIP is used to build HDF4 . The HDF-EOS2 needs to be built with the same type of SZIP used to build HDF4 . Any inconsistencies regarding the SZIP type will cause the failure of configure.

There are two ways to build HDF-EOS libraries. One way is to run the INSTALL-HDFEOS script. For detailed instructions, please read README under doc directory of the source distribution of the HDF-EOS2 library. Another way is to run configure and make. This is explained below.

The first step is to execute configure script included in the package. One option is required as a parameter to configure: CC. If HDF4 was built with SZIP, another option --with-szlib is required. The following is an example when HDF4 is built with SZIP.

If you are going to write a Fortran program and compile it with the HDF-EOS2 library, you need to build the HDF-EOS2 library with -Dfc2fortran option in CC like below: Alternatively, you can set the environment variables instead of suppying the above options. In csh or tcsh, you run the following commands: In sh or bash, you run the following commands: You should replace <hdf4_path> and <szip_path> by proper paths in the above command. The configure script will check your system, and generate Makefile. If configure generates some errors, please carefully check the error message. It is very possible that you may need to correctly set other flags, such as CFLAGS, FFLAGS and LDFLAGS. For example, some systems may have a C compiler or Fortran compiler that generates either 32-bit binary or 64-bit binary depending on those flags.

After configuration, one can build HDF-EOS2 using make. If you downloaded code for test drivers, you can also test if the library works as expected by running make check. Running make install will install the HDF-EOS2 library.

For more information on how to use auto-configuration to build the HDF-EOS2 library, check the text file AUTOCONF_INSTALL under doc directory of the source distribution of the HDF-EOS2 library.

HDF-EOS5

You can get the latest release from here. As of July 2009, HDF-EOS 5.1.12 is the latest version, and you can get the library from their ftp site. There are two tar files for UNIX; one contains source code and sample code, and the other contains code for test drivers.

Because HDF-EOS5 is built on HDF5 , the HDF5 library is required to build the HDF-EOS5 library. HDF5 can optionally be built with the SZIP compression library. If SZIP was used, you need to know the library path. Due to the license issue, there are two types of SZIP libraries: decoder only and encoder/decoder. You need to know which type of SZIP is used to build HDF5 . The HDF-EOS5 needs to be built with the same type of SZIP used to build HDF5 . Any inconsistencies regarding the SZIP type will cause the failure of configure.

The first step is to execute configure script included in the package. One option is required as a parameter to configure: CC. If HDF5 is 1.8 or higher, one needs to define H5_USE_16_API preprocessor macro as CFLAGS. This is because HDF-EOS5 uses HDF5 1.6 API and this is not compatible with HDF5 1.8 API. If HDF5 was built with SZIP, another option --with-szlib is required. The following is an example when HDF5 1.8 is built with SZIP.

If you are going to write a Fortran program and compile it with the HDF-EOS5 library, you need to build the HDF-EOS5 library with -Dfc2fortran option in CC like below: Alternatively, you can set the environment variables instead of suppying the above options. In csh or tcsh, you run the following commands: In sh or bash, you run the following commands: You should replace <hdf5_path> and <szip_path> by proper paths in the above command. The configure script will check your system, and generate Makefile. If configure generates some errors, please carefully check the error message. It is very possible that you may need to correctly set other flags, such as CFLAGS, FFLAGS and LDFLAGS. For example, some systems may have a C compiler or Fortran compiler that generates either 32-bit binary or 64-bit binary depending on those flags.

After configuration, one can build HDF-EOS5 using make. If you downloaded test drivers, you can also test if the library works as expected by running make check. Running make install will install the HDF-EOS5 library.

For more information on how to use auto-configuration to build the HDF-EOS5 library, check the text file AUTOCONF_INSTALL under doc directory of the source distribution of the HDF-EOS5 library.

Last modified: 10/06/2010