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.
> New Staff Reply: libnetcdff ?? > > Howdy Russ! > > Thanks for finding that! I was sure I mentioned it somewhere, but could > not find it. > > Of course, rather than post some justification for myself I am more > interested in finding an answer. ;-) > > As you'll know if your reading your mail in order, I think I have found > one. Unfortunately it perpetrates a bad practice, but will help modelers > such as the irate user cited. Yes, thanks for doing this unsavory thing! But I have a question. If someone uses this and has some netCDF f90 code, can they build the f90 library as a separate library that calls the combined C/f77 library, and link their application to the two resulting libraries? I understand that this would be stupid, they should just build/install the C library first and then the separate Fortran library and link to those two resulting libraries, I'm just curious if it would work, for people who have their own netCDF f90 applications to run on a platform where the kluge C/f77 library has been installed. --Russ > Thanks, > > Ed > -- > Ed Hartnett -- address@hidden > > > > Ticket Details > =================== > Ticket ID: KGN-827851 > Department: Support netCDF > Priority: Normal > Status: Open > Link: https://www.unidata.ucar.edu/esupport/staff/index.php?_m=tickets&_a=vi > ewticket&ticketid=18781 Ticket Details =================== Ticket ID: KGN-827851 Department: Support netCDF Priority: Normal Status: Open