Applications that were created with earlier HDF5 releases may not compile with 1.14 by default.
The API Compatibility Macros in HDF5 allow users to work around this issue. Users can specify a compatibility macro mapping for the version of HDF5 that an application was built with. For example, a 1.10 application can be built with 1.14 using either an application or library mapping as follows:
However, users will not be able to take advantage of some of the new features in 1.14 if using these compatibility mappings.
See the Migrating from HDF5 1.12 to HDF5 1.14 page for details on upgrading an application.
The pre-built binary distributions in the table below contain the HDF5 libraries, include files, utilities, and release notes, and are built with the SZIP Encoder Enabled and ZLIB external libraries. For information on using SZIP, see the SZIP licensing information. Additional binaries can be found on our ftp site. The filter plugins for 1.14.0 are included in the files below
Windows Note: The HDF Group uses an installer program to install the HDF5 libraries, header and support files on Windows. This installer is digitally signed by The HDF Group. Please be aware that the installer requires that the user have permission to install files on the target computer. Also note that the Windows binary distributions are built in Release mode with debugging symbols. Please avoid using spaces in directory path names as this can cause problems when building.
To use the shared libraries on Windows with Visual Studio you must specify the
H5_BUILT_AS_DYNAMIC_LIB compile definition.
Static libraries begin with lib and shared libraries do not. For example,
hdf5.lib is the shared library and
libhdf5.lib is the static library.
You can access all versions of HDF5 on the portal.