NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Thanks, I noticed the same problem, and I agree - having nc-config call nf-config would be a nice backward compatible solution. Jim On Sun, Mar 25, 2012 at 4:10 AM, Thomas Orgis <thomas.orgis@xxxxxx> wrote: > Am Sun, 25 Mar 2012 12:02:26 +0200 > schrieb Thomas Orgis <Thomas.Orgis@xxxxxx>: > > > shell$ nc-config --flibs > > -L/some/path/lib @NC_FLIBS@ > > Oh, I see ... there is nf-config now. I have to adapt my Makefile, then, > for another case. Now it would be rather smart if nc-config would call > nf-config transparently for fortran stuff, eh? Even better: What exactly > is the reason not to provide files for pkg-config instead? Now we have two > config scripts for NetCDF, I guess three with the C++ interface. It gets > messy and I wonder what for. > > But, well, putting a hint about nf-config in some docs would also be > nice... it may be obvious, but I was not looking for it; just trying to get > NetCDF re-installed quickly to get working Fortran module again (because of > non-existent binary compatibility even between versions of the same > compiler). > > > Alrighty then, > > Thomas > > -- > Thomas Orgis, Dipl. Physiker > Alfred-Wegener-Institut für Polar- und Meeresforschung Potsdam > > _______________________________________________ > netcdfgroup mailing list > netcdfgroup@xxxxxxxxxxxxxxxx > For list information or to unsubscribe, visit: > http://www.unidata.ucar.edu/mailing_lists/ > -- Jim Edwards CESM Software Engineering Group National Center for Atmospheric Research Boulder, CO 303-497-1842
netcdfgroup
archives: