Changes between Version 12 and Version 13 of HDF

Timestamp:

Nov 6, 2011, 11:28:44 AM (12 years ago)

Author:

etourigny

Comment:

--

HDF

@@ -24 +24 @@
 == Incompatibility with NetCDF Libraries == 
 
-The HDF4 libraries include an implementation of the netcdf api which can access hdf files.  If building with HDF4 and NetCDF it is necessary to build the HDF library with this disable.  This can be accomplished by defining the macro HAVE_NETCDF when building the HDF libraries.  I normally accomplish this by configuring the HDF4 libraries as follows:
+The HDF4 libraries include an implementation of the netcdf api which can access hdf files.  If building with HDF4 and NetCDF it is necessary to build the HDF library with this disabled.  
+
+If using Ubuntu/Debian dev packages you must make sure that the libhdf4-alt-dev package is installed instead of the libhdf4-dev package.
+
+If building HDF4 manually you have to add "--disable-netcdf" to "configure" and HDF4 will move its embedded NetCDF functions in a different private namespace to avoid name clashes.
+
+
+{{{
+./configure --disable-netcdf --disable-fortran
+}}}  
+
+If building older versions of HDF4 (before HDF4.2r3) the macro HAVE_NETCDF needs to be defined instead.  This can be accomplished by configuring the HDF4 libraries as follows:
 
 {{{
@@ -33 +44 @@
 }}}
 
-The -fPIC and LIBS may not be necessary on all platforms.  Without this fix either GDAL will crash intermittently when accessing netcdf files, or the build of GDAL will fail. On more recent HDF4 releases it has been added a new configuration flag, so that you have
-to use
-
-{{{
-./configure --disable-netcdf --disable-fortran
-}}}  
-
-and HDF4 will move its embedded NetCDF functions in a different private namespace to avoid name clashes.
+The -fPIC and LIBS may not be necessary on all platforms.  Without this fix either GDAL will crash intermittently when accessing netcdf files, or the build of GDAL will fail. 
 
 == Potential conflicts with internal libz ==