8d7d5ac9e5
The current method of setting the `HDF5_HAS_PAR_FILTERS` and `HAS_PAR_FILTERS` variables is done purely based on the `HDF5_VERSION` and that variable is only set inside the if block which finds the HDF5 library based on CMake package files. If the user specifies the explicit location of the HDF5 library and include files (for example, via:
```
-DHDF5_C_LIBRARY:PATH=${INSTALL_PATH}/lib/libhdf5.${LD_EXT} \
-DHDF5_HL_LIBRARY:PATH=${INSTALL_PATH}/lib/libhdf5_hl.${LD_EXT} \
-DHDF5_INCLUDE_DIR:PATH=${INSTALL_PATH}/include
```
Then, the code path which determines whether the par filters variables is set is not run. However, later on in the file, there is another check for parallel filter support (near line 759):
```
# Check to see if this is hdf5-1.10.3 or later.
CHECK_LIBRARY_EXISTS(${HDF5_C_LIBRARY_hdf5} H5Dread_chunk "" HDF5_SUPPORTS_PAR_FILTERS)
```
This PR moves the code that sets the two other par filters variables down after this check and instead of setting their values based on the version, it bases it on the results of this test.
I'm not totally sure why there are three variables; it looks like the `HDF5_SUPPORTS_PAR_FILTERS` and `HDF5_HAS_PAR_FILTERS` could be combined. I think the `HAS_PAR_FILTERS` is a string which is used to show the results of the configuration and the other two are booleans.
The new check should work for both types of HDF5 installs (cmake-based and configure-based)
|
||
|---|---|---|
| .github | ||
| cmake | ||
| conda.recipe | ||
| ctest_scripts | ||
| dap4_test | ||
| debug | ||
| docs | ||
| examples | ||
| h5_test | ||
| hdf4_test | ||
| include | ||
| libdap2 | ||
| libdap4 | ||
| libdispatch | ||
| libhdf4 | ||
| libhdf5 | ||
| liblib | ||
| libsrc | ||
| libsrc4 | ||
| libsrcp | ||
| nc_perf | ||
| nc_test | ||
| nc_test4 | ||
| ncdap_test | ||
| ncdump | ||
| ncgen | ||
| ncgen3 | ||
| nctest | ||
| NUG | ||
| oc2 | ||
| plugins | ||
| unit_test | ||
| .gitignore | ||
| .travis.yml | ||
| acinclude.m4 | ||
| appveyor.yml | ||
| bootstrap | ||
| cmake_uninstall.cmake.in | ||
| CMakeInstallation.cmake | ||
| CMakeLists.txt | ||
| COMPILE.cmake.txt | ||
| config.h.cmake.in | ||
| config.h.cmake.in.old-works | ||
| configure.ac | ||
| COPYRIGHT | ||
| CTestConfig.cmake.in | ||
| CTestCustom.cmake | ||
| dods.m4 | ||
| FixBundle.cmake.in | ||
| INSTALL.md | ||
| lib_flags.am | ||
| libnetcdf.settings.in | ||
| Makefile.am | ||
| mclean | ||
| nc-config.cmake.in | ||
| nc-config.in | ||
| netcdf.pc.in | ||
| netCDFConfig.cmake.in | ||
| PostInstall.cmake | ||
| postinstall.sh.in | ||
| README.md | ||
| RELEASE_NOTES.md | ||
| test_common.in | ||
| test_prog.c | ||
| test-driver-verbose | ||
| wjna | ||
Unidata NetCDF
About
The Unidata network Common Data Form (netCDF) is an interface for scientific data access and a freely-distributed software library that provides an implementation of the interface. The netCDF library also defines a machine-independent format for representing scientific data. Together, the interface, library, and format support the creation, access, and sharing of scientific data. The current netCDF software provides C interfaces for applications and data. Separate software distributions available from Unidata provide Java, Fortran, Python, and C++ interfaces. They have been tested on various common platforms.
Properties
NetCDF files are self-describing, network-transparent, directly
accessible, and extendible. Self-describing means that a netCDF file
includes information about the data it contains. Network-transparent
means that a netCDF file is represented in a form that can be accessed
by computers with different ways of storing integers, characters, and
floating-point numbers. Direct-access means that a small subset of a
large dataset may be accessed efficiently, without first reading through
all the preceding data. Extendible means that data can be appended to
a netCDF dataset without copying it or redefining its structure.
Use
NetCDF is useful for supporting access to diverse kinds of scientific data in heterogeneous networking environments and for writing application software that does not depend on application-specific formats. For information about a variety of analysis and display packages that have been developed to analyze and display data in netCDF form, see
More information
For more information about netCDF, see
Latest releases
You can obtain a copy of the latest released version of netCDF software for various languages:
Copyright
Copyright and licensing information can be found here, as well as in the COPYRIGHT file accompanying the software
Installation
To install the netCDF-C software, please see the file INSTALL in the netCDF-C distribution, or the (usually more up-to-date) document:
Documentation
A language-independent User's Guide for netCDF, and some other language-specific user-level documents are available from:
- Language-independent User's Guide
- NetCDF-C Tutorial
- Fortran-90 User's Guide
- Fortran-77 User's Guide
- netCDF-Java/Common Data Model library
- netCDF4-python
A mailing list, netcdfgroup@unidata.ucar.edu, exists for discussion of the netCDF interface and announcements about netCDF bugs, fixes, and enhancements. For information about how to subscribe, see the URL
Feedback
We appreciate feedback from users of this package. Please send comments, suggestions, and bug reports to support-netcdf@unidata.ucar.edu.