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.
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.
"Gregory Sjaardema" <gdsjaar@xxxxxxxxxx> writes: > On 9/6/11 4:22 PM, Ed Hartnett wrote: >> "Gregory Sjaardema"<gdsjaar@xxxxxxxxxx> writes: >> >>> We typically use non-shared library builds which need the hdf5 >>> specified explicitly. >>> --Greg >> For static builds, the nc-config program should list all libraryes, >> including the HDF5 one... >> >> Ed >> > OK, sorry for the confusion. If I do build just the static library > (--disable-shared), then nc-config does show all of the libraries. > However, if I build both shared and static, then nc-config shows only > the netcdf library. In my use, we install both shared and static > libraries and some applications link to the shared and some to the > static and they need some way to get all of the library information > from the nc-config... > > Thanks, > --Greg Ah ha! Now I get it. So would you like to have all libraries listed, even for shared builds? I believe this will be harmless... Anyone else have a preference on this? Thanks, Ed -- Ed Hartnett -- ed@xxxxxxxxxxxxxxxx
netcdfgroup archives: