A CTest script and platform configuration file can be used to simplify building with CMake. The script below will build HDF4 with SZIP, ZLIB, and the JPEG external libraries.
CMake MUST be installed. We recommend using version 3.10 or higher.
Blank spaces MUST NOT be used in directory path names as this will cause the build to fail.
Visual Studio Express users will not be able to package HDF into an install image executable. Turn off packaging by doing the following:
Create a working directory.
Uncompress the HDF4 CMake source code file into the working directory. It will contain a
CMake-hdf-N directory (where N is the release version).
From the command line, go into the
CMake-hdf-N directory, which contains:
HDF4 Source Code
User modifiable options
External library for JPEG Compression
External library for SZIP Compression
External library for ZLIB Compression
Users can change the options that HDF4 is built with by adding options to the build command (see the batch files/test script below) or by modifying the
HDF4options.cmake file. The
HDF4options.cmake file will override any options set in the configuration file. For more information see the How to Change HDF4 CMake Build Options page.
REQUIRED: Visual Studio Express users must change the build options to turn off packaging or the build will fail.
Example build files are shown below:
|Platform||Batch File / Shell Script||ctest command|
|Windows 64-bit VS 2015||build-VS2015-64.bat||ctest -S HDF4config.cmake,BUILD_GENERATOR=VS201564 -C Release -V -O hdf4.log|
|Windows 32-bit VS 2015||build-VS2015-32.bat||ctest -S HDF4config.cmake,BUILD_GENERATOR=VS2015 -C Release -V -O hdf4.log|
|Unix||build-unix.sh||ctest -S HDF4config.cmake,BUILD_GENERATOR=Unix -C Release -V -O hdf4.log|
Where the ctest command is using these options:
hdf-4.2.N-<platform.<zip or tar.gz>
On Windows, a .msi or .exe file will also be created, depending on the installer. On Unix, an additional .sh file will be created.
If the built binary is not there, then see Troubleshooting for help.
libhdf4.settingsfile in the build directory. It contains information on how the binaries were built.
My platform/compiler is not included. Can I still use the configuration files?
Yes, you can but you will have to edit the
HDF4config.cmake file and update the variable:
Other variables may be updated for informational purposes but are not required (for example, SITE_OS_BITS).
The generators for your platform can be seen by typing:
What do I do if the build fails?
If the build works properly, then you will find the built and compressed binary in your
CMake-hdf-4.N directory. If you do not find it then check the log files. You will find those in the build directory under
CMake-hdf-4.N. For example, on Unix the log files will be in:
There are log files for the configure, test, and build.
What if the binary does not get packaged properly?
If the binary did not get packaged properly, look at the cpack.log file in the build directory under
CMake-hdf-4.N. For example, on Unix look here:
What do I do if I need to rebuild the software?
If you have to rebuild HDF4, remove the build directory first.
The library was built but there are no binaries. What do I do?
To install or package the binaries, run either make install or cpack in the build/ directory.