summaryrefslogtreecommitdiffstats
path: root/release_docs/README_HPC
diff options
context:
space:
mode:
authorDana Robinson <43805+derobins@users.noreply.github.com>2023-10-09 17:42:46 (GMT)
committerGitHub <noreply@github.com>2023-10-09 17:42:46 (GMT)
commit0feda66ff0dccdf77453b7c881c80be244e0ae12 (patch)
treec4a35a804bf18a5dac14aafae3f3e6e9281140ae /release_docs/README_HPC
parent7b18845e9c24cc0d910fa082d3f5c7c92797396d (diff)
downloadhdf5-0feda66ff0dccdf77453b7c881c80be244e0ae12.zip
hdf5-0feda66ff0dccdf77453b7c881c80be244e0ae12.tar.gz
hdf5-0feda66ff0dccdf77453b7c881c80be244e0ae12.tar.bz2
Bring the H5detect removal change from develop (#3648)
* Bring the H5detect removal change from develop - Removed CMake cross-compiling variables * HDF5_USE_PREGEN * HDF5_BATCH_H5DETECT These were used to work around H5detect and H5make_libsettings and are no longer required. - Running H5make_libsettings is no longer required for cross-compiling The functionality of H5make_libsettings is now handled via template files, so H5make_libsettings has been removed. - Running H5detect is no longer required for cross-compiling The functionality of H5detect is now exercised at library startup, so H5detect has been removed. * Put H5T_CONV_ab macros in do..while loops (#3432) Ever since a recent round of macro cleanup, bin/trace and clang-format have been bickering over what H5Tconv.c should look like and neither produces readable code. This change puts the top-level H5T_CONV_ab macros in do..while loops, adds appropriate semicolons, and adds the missing H5_CLANG_DIAG_ON|OFF and H5_GCC_CLANG_DIAG_ON|OFF macros to the list of statement macros clang-format recognizes. H5Tconv.c is now readable and both bin/trace and clang-format are happy.
Diffstat (limited to 'release_docs/README_HPC')
-rw-r--r--release_docs/README_HPC19
1 files changed, 0 insertions, 19 deletions
diff --git a/release_docs/README_HPC b/release_docs/README_HPC
index 27dc32c..576e019 100644
--- a/release_docs/README_HPC
+++ b/release_docs/README_HPC
@@ -9,7 +9,6 @@ Section II: Obtain HDF5 source
Section III: Using ctest command to build and test
Section IV: Cross compiling
Section V: Manual alternatives
-Section VI: Other cross compiling options
************************************************************************
@@ -184,21 +183,3 @@ or
for parallel builds.
Tests on machines using LSF will typically use "bsub ctestS.lsf", etc.
-
-========================================================================
-VI. Other cross compiling options
-========================================================================
-Settings for two other cross-compiling options are also in the config/toolchain
-files which do not seem to be necessary with the Cray PrgEnv-* modules
-
-1. HDF5_USE_PREGEN. This option, along with the HDF5_USE_PREGEN_DIR CMake
- variable would allow the use of an appropriate H5Tinit.c file with type
- information generated on a compute node to be used when cross compiling
- for those compute nodes. The use of the variables in lines 110 and 111
- of HDF5options.cmake file seem to preclude needing this option with the
- available Cray modules and CMake option.
-
-2. HDF5_BATCH_H5DETECT and associated CMake variables. This option when
- properly configured will run H5detect in a batch job on a compute node
- at the beginning of the CMake build process. It was also found to be
- unnecessary with the available Cray modules and CMake options.