Repository navigation
Investigate using nc-config / nf-config to discover NetCDF libraries #36
Description
In some situations, typically HPC environments, this would avoid having to set -DNETCDF_DIR=.. / -DNETCDF_FORTRAN_DIR=...
Note that if netcdf-fortran is built with CMake, then nf-config --prefix just prints "not supported in CMake builds" or something similar.
Activity
zbeekman commentedon Jul 15, 2019
oh. sigh.
It's relatively easy to get CMake to generate pkg-config files. I wish NetCDF would install good/thorough CMake package config files and generate pkg-config files, then just abandon auto-tools. It would save everyone the hassle of having to write yet another FindNetCDF.cmake module. I've seen at least 4 popular versions floating around, each with its strengths and deficiencies. If NetCDF always used CMake, installed decent CMake pacakge config files and pkg-config files, and was smart enough to set
nf-config --prefixin CMake based builds, then the world would be a beautiful place.(i.e., you could adjust
CMAKE_PREFIX_PATHif needed andfind_package(NetCDF)would just work without having to roll your own find module.)dmey commentedon Nov 14, 2019
Could we not simply rely on
nc-configinstead ofnf-configand use it to infer the path to netcdf with the--fflagsand--flibs? But then again I think this would end up not being configured if users build NetCDF Fortran with CMake... . The question is whether all this is actually worth doing all this...If not I would probably just the hints to something like:
and then the user can simply pass
NETCDF_DIRandNETCDF_FORTRAN_DIRat configure time...letmaik commentedon Nov 14, 2019
@dmey Do you have a concrete situation where you're unable to use
NETCDF_DIR/NETCDF_FORTRAN_DIRon some system? Not sure why you mentionx86_64-linux-gnu.dmey commentedon Nov 14, 2019
Well this is why I suggested adding to
PATH_SUFFIXES ["x86_64-linux-gnu", ""]-- at the moment it would only work with"x86_64-linux-gnu", I think -- I am pretty sure I had this issue some time ago...