This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
> Afraid that attempting to compile from source was our only option, I > downloaded it. In the INSTALL file, section 3.8.3 says, > > "Due to the magic of libtool, the output files are found in the > libsrc/.libs directory. > > To get a MS compatible export library, open an MS DOS window, > change > directory to libsrc/.libs and run the following command: > > lib /machine:i386 /def:libnetcdf.def > > The above command uses the Microsoft LIB tool, which comes with > Visual C++.NET, and perhaps other Microsoft development tools. (To > get > this in my path, I open the "Visual Studio 2003 Command Prompt" in my > Windows program menu.) > > This command creates the .lib file, the import library, needed (or > at > least used) by MicroSoft (and other) build environments on Windows." > > > Apparently this step was skipped when producing most of the binaries: > 3.5.1, 3.6.3 fort & 3.6.2 PGI. It seems to have been done for 3.6.1, > but that binary does not include the Fortran interface, only C. Ok, I will try to get this fixed before the 3.7 release... > > It also turns out that I need a separate download for Visual Studio > support, so I'll try that next. > The same netCDF distribution works for both. See the win32/NET directory for the VS solution files for building netCDF. Thanks, Ed Ticket Details =================== Ticket ID: GCB-810427 Department: Support netCDF Priority: Normal Status: Open