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.
> Dear colleague, > > I am trying to compile a code that uses netCDF in a WinXP environment > using Compaq Visual Fortran 6.1.0 > I am not a Windows user, and I've found serious troubles. > > 1) All works perfectly in Linux/Unix/OS X, but there is no way to > link with none of the windows pre-compiled libraries I > found in internet. This is the typical error message: > > Linking... > read_NCEP1_data.Win.obj : error LNK2001: unresolved external symbol > _NF_OPEN@16 > read_NCEP1_grid.Win.obj : error LNK2001: unresolved external symbol > _NF_OPEN@16 Dr. Duran, Sorry that it has taken so long to get back to you. The windows port is a bit of a problem child. We are about to release the 4.1.1 version of netCDF, and then I will turn to the windows port again. The names of the fortran functions are controlled in the build by the setting of a pre-processor macro. Most fortran compilers work with either f2cFortran or pgiFortran. Two pre-built versions of the library are available for these two types of fortran compiler, but other compilers can be supported by building the project under the win32/NET directory of the 4.0.1 release, and changing the pre-processor flags in the properties window for the netcdf project. Thanks, Ed Ticket Details =================== Ticket ID: HOU-449074 Department: Support netCDF Priority: Critical Status: Closed