Currently, configure searches for the NetCDF header and library, and checks for various functions in order to determine what capabilities it has. However, nc-config, which comes with most (all?) NetCDF distributions already has this information.
This PR adds the flags --with-nc-config/--without-nc-config to ./configure. If --without-nc-config is specified, then configure uses the current method to determine functionality. Otherwise, it will use nc-config from either $PATH, or the path supplied to --with-nc-config=<path>. This always different NetCDF-C installations to be used, and not just the default system one.
Unfortunately, I don't know enough CMake to add it to that build system as well, but presumably this could be done.
Also, although it doesn't appear that you actually link against NetCDF-C, nc-config could also supply LDFLAGS, LIBS, CPPFLAGS if needed.
Currently,
configuresearches for the NetCDF header and library, and checks for various functions in order to determine what capabilities it has. However,nc-config, which comes with most (all?) NetCDF distributions already has this information.This PR adds the flags
--with-nc-config/--without-nc-configto./configure. If--without-nc-configis specified, thenconfigureuses the current method to determine functionality. Otherwise, it will usenc-configfrom either$PATH, or the path supplied to--with-nc-config=<path>. This always different NetCDF-C installations to be used, and not just the default system one.Unfortunately, I don't know enough CMake to add it to that build system as well, but presumably this could be done.
Also, although it doesn't appear that you actually link against NetCDF-C,
nc-configcould also supplyLDFLAGS, LIBS, CPPFLAGSif needed.