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.
> Hi Ed, > > Just a little follow-up explanation regarding the previous message. I > have noticed that the CVF linkage and the "Default" linkage used by > IFC yield different amounts of bytes in the function declaration > #bytes field (the @44, or @...whatever following the function names). > Somewhere I read this has something to do with "hidden" bytes used in > one case and not the other. > > Anyhow, if you could link the DLL with IFC default standard, then I > could try that out on the IFC compiler. That may very well work. > > Thanks. > > Steve > Howdy Steve! I have made a lot of progress with compiling netCDF under MinGW and getting DLLs. I now have DLLs that contain the nf_ functions as well as the nc_ functions. Try downloading this file and see if it works for you: ftp://ftp.unidata.ucar.edu/pub/netcdf/contrib/win32/win32_pgi_dll.tar.gz Please let me know if that works for you. Thanks! Ed Ticket Details =================== Ticket ID: KKK-748443 Department: Support netCDF Priority: Critical Status: Closed