netCDF driver: simplify identification logic by just checking runtime availability of HDF4/HDF5 drivers #10742
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.
... ignoring their compile-time availability, which makes it more robust in the case of plugin-only builds.
Also remove the GDAL_HAS_HDF4 and GDAL_HAS_HDF5 metadata items from the metadata of the netCDF driver. They are redundant with checking for GDALGetDriverByName("HDF4" / "HDF5") != nullptr.
CC @schwehr