[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[netCDF #IWF-312871]: issue with link to both NetCDF and HDF libraries
- To: Yaping.Li@xxxxxxxx
- Subject: [netCDF #IWF-312871]: issue with link to both NetCDF and HDF libraries
- From: "Unidata netCDF Support" <support-netcdf@xxxxxxxxxxxxxxxx>
- Date: Fri, 21 Mar 2008 15:40:30 -0600
- Delivered-to: support-netcdf@unidata.ucar.edu by laraine.unidata.ucar.edu (Postfix) with ESMTP id E18F2CB1CF; Fri, 21 Mar 2008 15:40:30 -0600 (MDT) id ADBFBD5116; Fri, 21 Mar 2008 15:40:30 -0600 (MDT)
Hi,
When you build the HDF4 library, you can use the -DHAVE_NETCDF option
for the C compiler, as described in this HDF Newsletter article:
http://hdf.ncsa.uiuc.edu/newsletters/newsletter21.html#2
And here's a little more information about a workaround for a problem
you may encounter when using that option:
http://www.unidata.ucar.edu/support/help/MailArchives/netcdf/msg02412.html
If you have the very latest version 4.2r3, they've changed the name of this
option:
- Modified the HDF4 mfhdf library and configure to work in the
absence of the NetCDF-3 header files when the HDF4 library
is configured with the --disable-netcdf flag. This feature is
required when building the ESDIS Toolkit in the presence of the
NetCDF-3 library. In this case, the HDF4 file netcdf.h is used
to build the HDF4 libraries and is installed under the name
"hdf4_netcdf.h" to avoid a name clash with the NetCDF-3 file
netcdf.h.
From ftp://ftp.hdfgroup.org/HDF/HDF_Current/src/RELEASE-4.2r3.txt
--Russ
--Russ
Russ Rew UCAR Unidata Program
russ@xxxxxxxxxxxxxxxx http://www.unidata.ucar.edu
Ticket Details
===================
Ticket ID: IWF-312871
Department: Support netCDF
Priority: Normal
Status: Closed