[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[netCDF #KPZ-969024]: guidance for netcdf libraries

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.

  • Subject: [netCDF #KPZ-969024]: guidance for netcdf libraries
  • Date: Fri, 28 Jul 2017 10:38:39 -0600
Hi David,

Can you describe a little more what you are seeing, and on what platform?  
There shouldn't be separate directories for the C and Fortran libraries, at 
least based on anything we have done.  I would expect to find them both in the 
same directory.  Once I have a better idea of what you're seeing, I will help 
you try to resolve this, because it doesn't sound quite right.  If this is the 
result of some change we made, it is unintended and will be reverted.  To 
answer your separate question, `nc-config` and `nf-config` will provide that 
information assuming they are on the system/user path.  But it shouldn't be 
necessary to use them to circumvent what you've observed!

Thanks,

-Ward

> Dear Unidata Helpers,
> 
> First there was only libnetcdf.a, then both libnetcdf.a and libnetcdff.a
> existed. Now there are completely separate directories for the C and
> Fortran libraries. This is getting confusing for our logic within our build
> systms because different sys admins are installing netcdf in different ways.
> 
> Other than having our Makefiles test on the the existence of a few likely
> library locations, is there a mechanism available to us so that we may
> interrogate a known file to get the information that we want? Basically, we
> want to link our source code with the netcdf libraries, and we need to know
> what and where those libraries are. Are there default environment variables
> that we can access?
> 
> Thanks much
> Dave
> 
> 


Ticket Details
===================
Ticket ID: KPZ-969024
Department: Support netCDF
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.