Merge branch 'HDFGroup:develop' into develop-s3-tools

Author: byrnHDF

.github/workflows/main-cmake.yml

@@ -39,8 +39,8 @@ jobs:
           - "MacOS Clang"
 
         # This is where we list the bulk of the options for each configuration.
-        # The key-value pair values are usually appropriate for being CMake or
-        # Autotools configure values, so be aware of that.
+        # The key-value pair values are usually appropriate for being CMake
+        # configure values, so be aware of that.
 
         include:
 

.github/workflows/tarball.yml

@@ -97,10 +97,10 @@ jobs:
           path: hdfsrc
           ref: '${{needs.check_commits.outputs.branch_ref }}'
 
-      - name: Install Autotools Dependencies (Linux, serial)
+      - name: Install Linux Dependencies (Linux, serial)
         run: |
              sudo apt update
-             sudo apt install automake autoconf libtool libtool-bin gzip dos2unix
+             sudo apt install gzip dos2unix
 
       - name: Retrieve version
         id: version

.github/workflows/vol_adios2.yml

@@ -23,7 +23,7 @@ jobs:
       - name: Install dependencies
         run: |
           sudo apt-get update
-          sudo apt-get install automake autoconf libtool libtool-bin libopenmpi-dev
+          sudo apt-get install libopenmpi-dev
 
       - name: Checkout HDF5
         uses: actions/[email protected]

.github/workflows/vol_ext_passthru.yml

@@ -19,7 +19,7 @@ jobs:
       - name: Install dependencies
         run: |
           sudo apt-get update
-          sudo apt-get install automake autoconf libtool libtool-bin libopenmpi-dev
+          sudo apt-get install libopenmpi-dev
 
       - name: Checkout HDF5
         uses: actions/[email protected]

.github/workflows/vol_rest.yml

@@ -39,7 +39,7 @@ jobs:
       - name: Install dependencies
         run: |
           sudo apt-get update
-          sudo apt-get install automake autoconf libtool libtool-bin libcurl4-openssl-dev libyajl-dev
+          sudo apt-get install libcurl4-openssl-dev libyajl-dev
 
       - name: Checkout HDF5
         uses: actions/[email protected]

CONTRIBUTING.md

@@ -119,7 +119,6 @@ Please make sure that you check the items applicable to your pull request:
 * Code
   * [ ] Does the pull request have a corresponding GitHub issue and clear purpose?
   * [ ] Does the pull request follow HDF5 best practices (naming conventions, code portability, code structure, etc.)? <<TODO: link to the document>>
-  * [ ] If changes were done to Autotools build, were they added to CMake and vice versa?
   * [ ] Is the pull request applicable to any other branches? If yes, which ones? Please document it in the GitHub issue.
   * [ ] Is the new code sufficiently documented for future maintenance?
   * [ ] Does the new feature require a change to an existing API? See "API Compatibility Macros" document (https://hdfgroup.github.io/hdf5/develop/d7/d26/api-compat-macros.html)

README.md

@@ -14,7 +14,6 @@
 ![HDF5 Logo][u3]
 
 [![develop cmake build status](https://img.shields.io/github/actions/workflow/status/HDFGroup/hdf5/cmake.yml?branch=develop&label=HDF5%20develop%20CMake%20CI)](https://github.com/HDFGroup/hdf5/actions/workflows/cmake.yml?query=branch%3Adevelop)
-[![develop autotools build status](https://img.shields.io/github/actions/workflow/status/HDFGroup/hdf5/autotools.yml?branch=develop&label=HDF5%20develop%20Autotools%20CI)](https://github.com/HDFGroup/hdf5/actions/workflows/autotools.yml?query=branch%3Adevelop)
 [![HDF-EOS5 build status](https://img.shields.io/github/actions/workflow/status/HDFGroup/hdf5/hdfeos5.yml?branch=develop&label=HDF-EOS5)](https://github.com/HDFGroup/hdf5/actions/workflows/hdfeos5.yml?query=branch%3Adevelop)
 [![netCDF build status](https://img.shields.io/github/actions/workflow/status/HDFGroup/hdf5/netcdf.yml?branch=develop&label=netCDF)](https://github.com/HDFGroup/hdf5/actions/workflows/netcdf.yml?query=branch%3Adevelop)
 [![h5py build status](https://img.shields.io/github/actions/workflow/status/HDFGroup/hdf5/h5py.yml?branch=develop&label=h5py)](https://github.com/HDFGroup/hdf5/actions/workflows/h5py.yml?query=branch%3Adevelop)

doxygen/dox/HDF5CompressionTroubleshooting.dox

@@ -71,23 +71,7 @@ Everywhere in this document, the term \b szip refers to the \b szip filter and t
 \b gzip and \b szip require the \b libz.a(so,dylib,lib) and \b libsz.a(so,dylib,lib)/libaec.a(so,dylib,lib)
 libraries, respectively, to be present on the system and to be enabled during HDF5 configuration with
 this autotools configure command:
-\code
-    ./configure –with-zlib=/path… –with-szlib=/path… <other flags>
-\endcode
-There is one important difference in the behavior of GNU Autotools configure between \b gzip and \b szip.
-On Unix systems,\b  gzip compression is enabled automatically if the \b zlib library is present on the system
-in default locations without explicitly specifying <code>–with-zlib=/path</code>. For example, if
-<code>libz.so</code> is installed under <code>/usr/lib</code> with the
-header under <code>/usr/include</code> or under <code>/usr/local/lib</code> with the header under
-<code>/usr/local/include</code>, the following HDF5 configure command will find the \b gzip library and will
-configure the compression filter in: 
-\code
-    ./configure
-\endcode
-With GNU Autotools configure will not fail if libraries supporting the requested compression method are not found, for example,
-because a specified path was not correct, or the library is missing.
-
-Or CMake configure command:
+CMake configure command:
 \code
     cmake -G "Unix Makefiles" -DHDF5_ENABLE_ZLIB_SUPPORT=ON -DHDF5_ENABLE_SZIP_SUPPORT=ON -D<other flags>
 \endcode

doxygen/dox/branches-explained.dox

@@ -31,7 +31,7 @@ support.
 \section sec_branchexpl_release Release branches
 Release branches are used to prepare a new production release. They are primarily used to allow for
 last minute dotting of i's and crossing of t's 
-(things like setting the release version, finalizing release notes, and generating Autotools files)
+(things like setting the release version, finalizing release notes, and generating files)
 and do not include new development. 
 They are created from the maintenance branch at the time of the maintenance release and have 
 names like hdf5_1_10_N, where N is the minor release number. Once the release is  done it is

doxygen/dox/file-locking.dox

@@ -172,12 +172,6 @@ You can set the file locking defaults at configure time. This sets the defaults
 for the associated properties in the fapl. Users can override the configure
 defaults using #H5Pset_file_locking or the <code>HDF5_USE_FILE_LOCKING</code>
 environment variable.
-
-<h4>Autotools</h4>
-\li <code>--enable-file-locking=(yes</td><td>no</td><td>best-effort)</code> sets the file locking behavior.
-    <code>on</code> and <code>off</code> should be self-explanatory. <code>best-effort</code> turns file locking
-    on but ignores file locks when they are disabled (default: <code>best-effort</code>).
-
 <h4>CMake</h4>
 \li set <code>IGNORE_DISABLED_FILE_LOCK</code> to <code>ON</code> to ignore file locks when they
 \li  are disabled on the file system (default: <code>ON</code>).