Use nc-config in configure to check capabilities #39
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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, thenconfigure
uses the current method to determine functionality. Otherwise, it will usenc-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 supplyLDFLAGS, LIBS, CPPFLAGS
if needed.