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.
All, I recently grabbed netCDF-C v4.9.0 and netCDF-Fortran v4.6.0 and thought, heck, let's try to get zstd support as well! zstd built just fine and when I built netCDF-C it seemed pretty happy: ZSTD Support: yes but then when I tried to build netCDF-Fortran: configure: WARNING: ------------------------------------------ configure: WARNING: libnetcdf was built with zstd support, but HDF5_PLUGIN_PATH is not set. Either set the HDF5_PLUGIN_PATH environmental variable if zstandard tests fail, or use --disable-zstandard-plugin when running configure. configure: WARNING: ------------------------------------------ Okay. New to me. I then went back to the netCDF-C build and saw: checking whether dynamically loaded plugins is enabled... yes configure: WARNING: --disable-shared => --disable-plugins ... checking whether and where we should install plugins... no ... Plugin Install Prefix: N.A. Seeing that warning reminded me I build netCDF-C and netCDF-Fortran as a static library mainly for historical reasons (was static in the past and, well, if it works, don't mess with it unless you need to!) So I suppose the question is: Can I use zstd with a static build of netCDF? Or is it time to bite the bullet and reconfigure my software to use shared libraries... Matt -- Matt Thompson, SSAI, Ld Scientific Programmer/Analyst NASA GSFC, Global Modeling and Assimilation Office Code 610.1, 8800 Greenbelt Rd, Greenbelt, MD 20771 Phone: 301-614-6712 Fax: 301-614-6246 http://science.gsfc.nasa.gov/sed/bio/matthew.thompson
netcdfgroup
archives: