[Git][debian-gis-team/hdf4][experimental] 5 commits: New upstream version 4.3.1
Bas Couwenberg (@sebastic)
gitlab at salsa.debian.org
Tue Jul 1 04:34:32 BST 2025
Bas Couwenberg pushed to branch experimental at Debian GIS Project / hdf4
Commits:
fe1a39a4 by Bas Couwenberg at 2025-07-01T05:18:08+02:00
New upstream version 4.3.1
- - - - -
253f9aa2 by Bas Couwenberg at 2025-07-01T05:18:32+02:00
Update upstream source from tag 'upstream/4.3.1'
Update to upstream version '4.3.1'
with Debian dir 9ede479c07262a53388f980340f158532451766f
- - - - -
c187aa06 by Bas Couwenberg at 2025-07-01T05:29:46+02:00
New upstream release.
- - - - -
9e01ffaa by Bas Couwenberg at 2025-07-01T05:29:46+02:00
Drop obsolete patches.
- - - - -
20a1ef8a by Bas Couwenberg at 2025-07-01T05:30:04+02:00
Set distribution to experimental.
- - - - -
21 changed files:
- .github/workflows/tarball.yml
- HDF4Examples/Using_CMake.txt
- README.md
- config/cmake/examples/HDF4_Examples.cmake.in
- config/cmake/scripts/HDF4config.cmake
- configure
- configure.ac
- debian/changelog
- debian/control
- − debian/get-orig-source
- − debian/patches/enablesharedfortran.diff
- debian/patches/series
- − debian/patches/szlib.patch
- hdf/src/hfile.h
- hdf/src/vg.c
- mfhdf/test/tfile.c
- release_notes/INSTALL
- release_notes/INSTALL_CMake.txt
- release_notes/RELEASE.txt
- release_notes/USING_CMake_Examples.txt
- release_notes/USING_HDF4_CMake.txt
Changes:
=====================================
.github/workflows/tarball.yml
=====================================
@@ -119,7 +119,7 @@ jobs:
then
FILE_NAME_BASE=$(echo "snapshot")
else
- FILE_NAME_BASE=$(echo "hdf-${{ steps.version.outputs.SOURCE_TAG }}")
+ FILE_NAME_BASE=$(echo "hdf${{ steps.version.outputs.SOURCE_TAG }}")
fi
fi
echo "FILE_BASE=$FILE_NAME_BASE" >> $GITHUB_OUTPUT
@@ -143,7 +143,7 @@ jobs:
- name: Rename release file base name
id: ren-basename
- if: ${{ (inputs.use_environ == 'release') && (inputs.use_tag == 'snapshot') }}
+ if: ${{ (inputs.use_environ == 'release') }}
run: |
mv hdf-${{ steps.version.outputs.SOURCE_TAG }}.tar.gz ${{ inputs.use_tag }}.tar.gz
mv hdf-${{ steps.version.outputs.SOURCE_TAG }}.zip ${{ inputs.use_tag }}.zip
@@ -167,14 +167,14 @@ jobs:
uses: actions/upload-artifact at v4
with:
name: tgz-tarball
- path: ${{ steps.set-file-base.outputs.FILE_BASE }}.tar.gz
+ path: ${{ inputs.use_tag }}.tar.gz
if-no-files-found: error # 'warn' or 'ignore' are also available, defaults to `warn`
- name: Save zip-tarball
uses: actions/upload-artifact at v4
with:
name: zip-tarball
- path: ${{ steps.set-file-base.outputs.FILE_BASE }}.zip
+ path: ${{ inputs.use_tag }}.zip
if-no-files-found: error # 'warn' or 'ignore' are also available, defaults to `warn`
- name: Save tgz-tarball-nover
=====================================
HDF4Examples/Using_CMake.txt
=====================================
@@ -28,19 +28,32 @@ Notes: This short instruction is written for users who want to quickly build
I. Preconditions
========================================================================
- 1. We suggest you obtain the latest CMake for windows from the Kitware
+ 1. We suggest you obtain the latest CMake from the Kitware
web site. The HDF 4.3.x product requires a minimum CMake version
- of 3.12.
+ of 3.18. If you are using VS2022, the minimum CMake version is 3.21.
+ CMakePresets.json, requires CMake 3.25 or higher.
2. You have installed the HDF4 library built with CMake, by executing
the HDF Install Utility (the *.msi file in the binary package for
Windows or the *.sh on Linux). If you are using a Windows platform,
- you can obtain a pre-built Windows binary from The HDF Group's website
+ you can obtain a pre-built binary from The HDF Group's website
at www.hdfgroup.org.
- 3. Set the environment variable HDF4_DIR to the installed location of
- the config files for HDF4. On Windows:
- HDF4_ROOT=C:/Program Files/HDF_Group/HDF/4.3.x/
+ 3. Set the HDF4_ROOT CMake variable, -DHDF4_ROOT=<install_path>
+ or environment variable, set(ENV{HDF4_ROOT} "<install_path>")
+ to the installed location of HDF4.
+ On Windows:
+ HDF4_ROOT=C:/Program Files/HDF_Group/HDF4/z.y.x/
+ On unix:
+ HDF4_ROOT=<install root folder>/HDF_Group/HDF4/z.y.x/
+
+ If you are using shared libraries, you may need to add to the path
+ environment variable. Set the path environment variable to the
+ installed location of the library files for HDF4.
+ On Windows (*.dll):
+ PATH=%PATH%;C:/Program Files/HDF_Group/HDF4/z.y.x/bin
+ On unix (*.so):
+ LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<install root folder>/HDF_Group/HDF4/z.y.x/lib
(Note there are no quote characters used on Windows and all platforms
use forward slashes)
@@ -90,11 +103,14 @@ These steps are described in more detail below.
* MinGW Makefiles
* NMake Makefiles
* Unix Makefiles
- * Visual Studio 15
- * Visual Studio 15 Win64
- * Visual Studio 17
- * Visual Studio 17 Win64
- * Visual Studio 19
+ * Visual Studio 15 2017
+ * Visual Studio 15 2017 Win64
+ * Visual Studio 16 2019
+ * ... in addition VS2019 will need to set the "-A" option,
+ * ... [Win32, x64, ARM, ARM64]
+ * Visual Studio 17 2022
+ * ... in addition VS2022 will need to set the "-A" option,
+ * ... [Win32, x64, ARM, ARM64]
<options> is:
* H4EX_BUILD_TESTING:BOOL=ON
=====================================
README.md
=====================================
@@ -1,4 +1,4 @@
-HDF version 4.3.1-1 currently under development
+HDF version 4.3.1 released on 2025-06-30
=====================================
config/cmake/examples/HDF4_Examples.cmake.in
=====================================
@@ -30,12 +30,14 @@ if(DEFINED CTEST_SCRIPT_ARG)
endforeach()
endif()
-if(${CTEST_VSVERS} STREQUAL "64_VS2022") # 64-bit Visual Studio 2022
- set(CTEST_CMAKE_GENERATOR "Visual Studio 17 2022")
- set(CMAKE_GENERATOR_ARCHITECTURE "x64")
-elseif(${VS_VERS} STREQUAL "64_VS2019") # 64-bit Visual Studio 2019
- set(CTEST_CMAKE_GENERATOR "Visual Studio 16 2019")
- set(CMAKE_GENERATOR_ARCHITECTURE "x64")
+if(DEFINED CTEST_VSVERS)
+ if(${CTEST_VSVERS} STREQUAL "64_VS2022") # 64-bit Visual Studio 2022
+ set(CTEST_CMAKE_GENERATOR "Visual Studio 17 2022")
+ set(CMAKE_GENERATOR_ARCHITECTURE "x64")
+ elseif(${VS_VERS} STREQUAL "64_VS2019") # 64-bit Visual Studio 2019
+ set(CTEST_CMAKE_GENERATOR "Visual Studio 16 2019")
+ set(CMAKE_GENERATOR_ARCHITECTURE "x64")
+ endif()
endif()
###################################################################
=====================================
config/cmake/scripts/HDF4config.cmake
=====================================
@@ -33,7 +33,7 @@ cmake_minimum_required (VERSION 3.18)
##############################################################################
set (CTEST_SOURCE_VERSION "4.3.1")
-set (CTEST_SOURCE_VERSEXT "-1")
+set (CTEST_SOURCE_VERSEXT "")
##############################################################################
# handle input parameters to script.
=====================================
configure
=====================================
@@ -1,6 +1,6 @@
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.71 for HDF 4.3.1-1.
+# Generated by GNU Autoconf 2.71 for HDF 4.3.1.
#
# Report bugs to <help at hdfgroup.org>.
#
@@ -629,8 +629,8 @@ MAKEFLAGS=
# Identity of this package.
PACKAGE_NAME='HDF'
PACKAGE_TARNAME='hdf'
-PACKAGE_VERSION='4.3.1-1'
-PACKAGE_STRING='HDF 4.3.1-1'
+PACKAGE_VERSION='4.3.1'
+PACKAGE_STRING='HDF 4.3.1'
PACKAGE_BUGREPORT='help at hdfgroup.org'
PACKAGE_URL=''
@@ -1515,7 +1515,7 @@ if test "$ac_init_help" = "long"; then
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
-\`configure' configures HDF 4.3.1-1 to adapt to many kinds of systems.
+\`configure' configures HDF 4.3.1 to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
@@ -1586,7 +1586,7 @@ fi
if test -n "$ac_init_help"; then
case $ac_init_help in
- short | recursive ) echo "Configuration of HDF 4.3.1-1:";;
+ short | recursive ) echo "Configuration of HDF 4.3.1:";;
esac
cat <<\_ACEOF
@@ -1749,7 +1749,7 @@ fi
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
-HDF configure 4.3.1-1
+HDF configure 4.3.1
generated by GNU Autoconf 2.71
Copyright (C) 2021 Free Software Foundation, Inc.
@@ -2379,7 +2379,7 @@ cat >config.log <<_ACEOF
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
-It was created by HDF $as_me 4.3.1-1, which was
+It was created by HDF $as_me 4.3.1, which was
generated by GNU Autoconf 2.71. Invocation command line was
$ $0$ac_configure_args_raw
@@ -3667,7 +3667,7 @@ fi
# Define the identity of the package.
PACKAGE='hdf'
- VERSION='4.3.1-1'
+ VERSION='4.3.1'
printf "%s\n" "#define PACKAGE \"$PACKAGE\"" >>confdefs.h
@@ -20745,7 +20745,7 @@ Usage: $0 [OPTIONS]
Report bugs to <bug-libtool at gnu.org>."
lt_cl_version="\
-HDF config.lt 4.3.1-1
+HDF config.lt 4.3.1
configured by $0, generated by GNU Autoconf 2.71.
Copyright (C) 2011 Free Software Foundation, Inc.
@@ -24276,7 +24276,7 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
-This file was extended by HDF $as_me 4.3.1-1, which was
+This file was extended by HDF $as_me 4.3.1, which was
generated by GNU Autoconf 2.71. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
@@ -24344,7 +24344,7 @@ ac_cs_config_escaped=`printf "%s\n" "$ac_cs_config" | sed "s/^ //; s/'/'\\\\\\\\
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_cs_config='$ac_cs_config_escaped'
ac_cs_version="\\
-HDF config.status 4.3.1-1
+HDF config.status 4.3.1
configured by $0, generated by GNU Autoconf 2.71,
with options \\"\$ac_cs_config\\"
=====================================
configure.ac
=====================================
@@ -24,7 +24,7 @@
## NOTE: Do not forget to change the version number here when we do a
## release!!!
##
-AC_INIT([HDF], [4.3.1-1], [help at hdfgroup.org])
+AC_INIT([HDF], [4.3.1], [help at hdfgroup.org])
AC_CONFIG_SRCDIR([hdf/src/atom.c])
AC_CONFIG_HEADERS([hdf/src/h4config.h])
=====================================
debian/changelog
=====================================
@@ -1,7 +1,7 @@
-libhdf4 (4.3.1~20250626143346-88d85d359-1) UNRELEASED; urgency=medium
+libhdf4 (4.3.1-1~exp1) experimental; urgency=medium
* Team upload.
- * New upstream git snapshot.
+ * New upstream release.
(closes: #1097195)
* Bump Standards-Version to 4.7.2, no changes.
* Fix old FSF address in copyright file.
@@ -11,8 +11,9 @@ libhdf4 (4.3.1~20250626143346-88d85d359-1) UNRELEASED; urgency=medium
* Don't include .la file in -dev package.
* Remove generated files in clean target.
* Replace obsolete Breaks/Conflicts/Replaces.
+ * Drop obsolete patches.
- -- Bas Couwenberg <sebastic at debian.org> Thu, 26 Jun 2025 17:29:55 +0200
+ -- Bas Couwenberg <sebastic at debian.org> Tue, 01 Jul 2025 05:29:49 +0200
libhdf4 (4.3.0-1) unstable; urgency=medium
=====================================
debian/control
=====================================
@@ -45,8 +45,8 @@ Depends: libhdf4-0 (= ${binary:Version}),
libjpeg-dev,
zlib1g-dev,
${misc:Depends}
-Breaks: libhdf4-alt-dev (<< 4.3.1~)
-Replaces: libhdf4-alt-dev (<< 4.3.1~)
+Breaks: libhdf4-alt-dev (<< 4.3.1)
+Replaces: libhdf4-alt-dev (<< 4.3.1)
Description: Hierarchical Data Format development files
HDF is a multi-object file format for storing and transferring
graphical and numerical data mainly used in scientific computing. HDF
=====================================
debian/get-orig-source deleted
=====================================
@@ -1,19 +0,0 @@
-#!/bin/bash
-
-REMOTE=upstream
-BRANCH=${REMOTE}/hdf_4_3_1
-
-if [ $(git remote show ${REMOTE} | wc -l) -eq 0 ]; then
- git remote add ${REMOTE} https://github.com/HDFGroup/hdf4.git
-fi
-
-git fetch ${REMOTE} --no-tags
-
-PACKAGE=$(dpkg-parsechangelog -S Source)
-
-COMMIT=$(git log -n1 --format=format:%h ${BRANCH})
-DATE=$(date +%Y%m%d%H%M%S --date="@$(git log -n1 --format=format:%ct ${BRANCH})")
-
-VERSION="4.3.1~${DATE}-${COMMIT}"
-
-git archive --format=tar.gz --prefix=${PACKAGE}-${VERSION}/ -o ../${PACKAGE}_${VERSION}.orig.tar.gz ${BRANCH}
=====================================
debian/patches/enablesharedfortran.diff deleted
=====================================
@@ -1,32 +0,0 @@
-Description: Enable support for shared fortran libraries.
-Author: Johan Van de Wauw <johan.vandewauw at gmail.com>
-Forwarded: not-needed
-
---- a/configure.ac
-+++ b/configure.ac
-@@ -332,15 +332,16 @@ AC_SUBST([BUILD_FORTRAN])
- ## Build static libraries by default. Furthermore, fortran shared libraries
- ## are unsupported. Disallow a user from enabling both shared libraries and
- ## fortran.
--if test "X${enable_shared}" != "Xyes"; then
-- enable_shared="no"
--fi
--
--if test "X${enable_shared}" = "Xyes"; then
-- if test "X${BUILD_FORTRAN}" = "Xyes"; then
-- AC_MSG_ERROR([Cannot build shared fortran libraries. Please configure with --disable-fortran flag.])
-- fi
--fi
-+#this test is overwritten in debian - we allow shared fortran libraries
-+#if test "X${enable_shared}" != "Xyes"; then
-+# enable_shared="no"
-+#fi
-+#
-+#if test "X${enable_shared}" = "Xyes"; then
-+# if test "X${BUILD_FORTRAN}" = "Xyes"; then
-+# AC_MSG_ERROR([Cannot build shared fortran libraries. Please configure with --disable-fortran flag.])
-+# fi
-+#fi
-
- ## ----------------------------------------------------------------------
- ## Check if they would like the Java native interface (JNI) compiled
=====================================
debian/patches/series
=====================================
@@ -1,3 +1 @@
-enablesharedfortran.diff
reproducible-builds.patch
-szlib.patch
=====================================
debian/patches/szlib.patch deleted
=====================================
@@ -1,44 +0,0 @@
-Description: Fix FTBFS when szip is enabled.
- /usr/bin/ld: ../../hdf/src/.libs/libdf.so: undefined reference to `SZ_encoder_enabled'
- /usr/bin/ld: ../../hdf/src/.libs/libdf.so: undefined reference to `SZ_BufftoBuffCompress'
- /usr/bin/ld: ../../hdf/src/.libs/libdf.so: undefined reference to `SZ_BufftoBuffDecompress'
- .
- /usr/bin/ld: hrepack_parse.o: undefined reference to symbol 'SZ_encoder_enabled'
- /usr/bin/ld: /lib/x86_64-linux-gnu/libsz.so.2: error adding symbols: DSO missing from command line
- .
- /usr/bin/ld: hrepacktst.o: undefined reference to symbol 'SZ_encoder_enabled'
- /usr/bin/ld: /lib/x86_64-linux-gnu/libsz.so.2: error adding symbols: DSO missing from command line
-Author: Bas Couwenberg <sebastic at debian.org>
-Forwarded: https://github.com/HDFGroup/hdf4/pull/716
-
---- a/hdf/src/Makefile.am
-+++ b/hdf/src/Makefile.am
-@@ -34,6 +34,8 @@ libdf_la_SOURCES = $(CSOURCES)
- include_HEADERS = $(CHEADERS)
- endif
-
-+libdf_la_LIBADD = @LIBS@
-+
- # The following is a workaround. Since Fortran is included in this
- # Makefile.am, automake will always try to use the Fortran linker, even when
- # fortran has been disabled in configure. The Fortran linker gets confused
---- a/mfhdf/hrepack/Makefile.am
-+++ b/mfhdf/hrepack/Makefile.am
-@@ -26,7 +26,7 @@ hrepack_SOURCES = hrepack.c hrepack_an.c
- hrepack_opttable.c hrepack_parse.c \
- hrepack_sds.c hrepack_utils.c \
- hrepack_vg.c hrepack_vs.c hrepack_dim.c
--hrepack_LDADD = $(LIBMFHDF) $(LIBHDF)
-+hrepack_LDADD = $(LIBMFHDF) $(LIBHDF) @LIBS@
- hrepack_DEPENDENCIES = $(LIBMFHDF) $(LIBHDF)
-
- #############################################################################
-@@ -39,7 +39,7 @@ check_SCRIPTS=hrepack.sh
- check_PROGRAMS = hrepack_check test_hrepack
-
- test_hrepack_SOURCES = hrepacktst.c
--test_hrepack_LDADD = $(LIBMFHDF) $(LIBHDF) -lm
-+test_hrepack_LDADD = $(LIBMFHDF) $(LIBHDF) -lm @LIBS@
- test_hrepack_DEPENDENCIES = $(LIBMFHDF) $(LIBHDF)
-
- hrepack_check_SOURCES = hrepack_check.c
=====================================
hdf/src/hfile.h
=====================================
@@ -26,9 +26,9 @@
#define LIBVER_MAJOR 4
#define LIBVER_MINOR 3
#define LIBVER_RELEASE 1
-#define LIBVER_SUBRELEASE "1" /* For pre-releases like snap0 */
- /* Empty string for real releases */
-#define LIBVER_STRING "HDF Version 4.3 Release 1-1, April 11, 2025"
+#define LIBVER_SUBRELEASE "" /* For pre-releases like snap0 */
+ /* Empty string for real releases */
+#define LIBVER_STRING "HDF Version 4.3 Release 1, June 27, 2025"
#define LIBVSTR_LEN 80 /* Length of version string */
#define LIBVER_LEN 92 /* 4+4+4+80 = 92 */
/* end of version tags */
=====================================
hdf/src/vg.c
=====================================
@@ -679,6 +679,14 @@ DESCRIPTION
Get information about Vdata. Space for 'fields' and 'vsname'
must be allocated by user.
+ VSinquire returns FAIL when any of the requested information is
+ not retrievable, meaning some of the information may still be
+ good even when the function returns FAIL.
+
+ We assume that 'fields' and 'vsname' buffers have been allocated by
+ the caller. When any of the arguments is null, no information will be
+ returned for it.
+
RETURNS
SUCCEED/FAIL
@@ -700,7 +708,7 @@ VSinquire(int32 vkey, /* IN: vdata key */
/* obtain the value for each parameter although the previous one
fails; ret_value should be FAIL if any of the parameters fails */
- if (fields) { /* we assume 'fields' space has been pre-allocated by user? */
+ if (fields) {
status = VSgetfields(vkey, fields);
ret_value = (status == FAIL) ? FAIL : ret_value;
}
@@ -716,7 +724,7 @@ VSinquire(int32 vkey, /* IN: vdata key */
*eltsize = VSsizeof(vkey, fields);
ret_value = (*eltsize == FAIL) ? FAIL : ret_value;
}
- if (vsname) { /* we assume 'vsname' space as been pre-allocated by user? */
+ if (vsname) {
status = VSgetname(vkey, vsname);
ret_value = (status == FAIL) ? FAIL : ret_value;
}
=====================================
mfhdf/test/tfile.c
=====================================
@@ -189,12 +189,12 @@ test_max_open_files()
/* Get the current max and system limit */
status = SDget_maxopenfiles(&curr_max, &sys_limit);
- CHECK(status, FAIL, "test_maxopenfiles: SDget_maxopenfiles");
- VERIFY(curr_max, H4_MAX_NC_OPEN, "test_maxopenfiles: SDreset_maxopenfiles");
+ CHECK(status, FAIL, "test_max_open_files: SDget_maxopenfiles");
+ VERIFY(curr_max, H4_MAX_NC_OPEN, "test_max_open_files: SDget_maxopenfiles");
/* Reset current max to an arbitrary number and check */
curr_max = SDreset_maxopenfiles(33);
- VERIFY(curr_max, 33, "test_maxopenfiles: SDreset_maxopenfiles");
+ VERIFY(curr_max, 33, "test_max_open_files: SDreset_maxopenfiles");
/* Try to create more files than the default max (currently, 32) and
all should succeed */
@@ -202,53 +202,53 @@ test_max_open_files()
/* Create a file */
sprintf(filename[index], "file%i", index);
fids[index] = SDstart(filename[index], DFACC_CREATE);
- CHECK(fids[index], FAIL, "test_maxopenfiles: SDstart");
+ CHECK(fids[index], FAIL, "test_max_open_files: SDstart");
}
/* Verify that NUM_FILES_LOW files are opened */
curr_opened = SDget_numopenfiles();
- VERIFY(curr_opened, NUM_FILES_LOW, "test_maxopenfiles: SDget_numopenfiles");
+ VERIFY(curr_opened, NUM_FILES_LOW, "test_max_open_files: SDget_numopenfiles");
/* Now randomly close 3 files and check number of opened files */
status = SDend(fids[5]);
- CHECK(status, FAIL, "test_maxopenfiles: SDend");
+ CHECK(status, FAIL, "test_max_open_files: SDend");
status = SDend(fids[15]);
- CHECK(status, FAIL, "test_maxopenfiles: SDend");
+ CHECK(status, FAIL, "test_max_open_files: SDend");
status = SDend(fids[25]);
- CHECK(status, FAIL, "test_maxopenfiles: SDend");
+ CHECK(status, FAIL, "test_max_open_files: SDend");
curr_opened = SDget_numopenfiles();
- VERIFY(curr_opened, NUM_FILES_LOW - 3, "test_maxopenfiles: SDget_numopenfiles");
+ VERIFY(curr_opened, NUM_FILES_LOW - 3, "test_max_open_files: SDget_numopenfiles");
/* Get the current max and system limit */
status = SDget_maxopenfiles(&curr_max, &sys_limit);
- CHECK(status, FAIL, "test_maxopenfiles: SDget_maxopenfiles");
- VERIFY(curr_max, sys_limit, "test_maxopenfiles: SDget_maxopenfiles");
+ CHECK(status, FAIL, "test_max_open_files: SDget_maxopenfiles");
+ VERIFY(curr_max, sys_limit, "test_max_open_files: SDget_maxopenfiles");
/* Get the current max another way, it should be the system limit */
curr_max = SDreset_maxopenfiles(0);
- VERIFY(curr_max, sys_limit, "test_maxopenfiles: SDreset_maxopenfiles");
+ VERIFY(curr_max, sys_limit, "test_max_open_files: SDreset_maxopenfiles");
/* Reopen the 3 files above, and check the number of opened files again */
fids[5] = SDstart(filename[5], DFACC_RDWR);
- CHECK(fids[5], FAIL, "test_maxopenfiles: SDstart");
+ CHECK(fids[5], FAIL, "test_max_open_files: SDstart");
fids[15] = SDstart(filename[15], DFACC_RDWR);
- CHECK(fids[15], FAIL, "test_maxopenfiles: SDstart");
+ CHECK(fids[15], FAIL, "test_max_open_files: SDstart");
fids[25] = SDstart(filename[25], DFACC_RDWR);
- CHECK(fids[25], FAIL, "test_maxopenfiles: SDstart");
+ CHECK(fids[25], FAIL, "test_max_open_files: SDstart");
curr_opened = SDget_numopenfiles();
- VERIFY(curr_opened, NUM_FILES_LOW, "test_maxopenfiles: SDget_numopenfiles");
+ VERIFY(curr_opened, NUM_FILES_LOW, "test_max_open_files: SDget_numopenfiles");
/* Reset current max to a value that is smaller than the current
number of opened files; it shouldn't reset */
curr_max_bk = curr_max;
curr_max = SDreset_maxopenfiles(curr_opened - 1);
- VERIFY(curr_max, curr_max_bk, "test_maxopenfiles: SDreset_maxopenfiles");
+ VERIFY(curr_max, curr_max_bk, "test_max_open_files: SDreset_maxopenfiles");
/* Reset current max again to a value that is smaller than the
current max but larger than the current number of opened files,
that should work for there is no information loss */
curr_max = SDreset_maxopenfiles(curr_opened + 3);
- VERIFY(curr_max, curr_opened + 3, "test_maxopenfiles: SDreset_maxopenfiles");
+ VERIFY(curr_max, curr_opened + 3, "test_max_open_files: SDreset_maxopenfiles");
/* Try to create more files up to the system limit or NUM_FILES_HI,
because the arrays have max NUM_FILES_HI elements in this test */
@@ -268,23 +268,23 @@ test_max_open_files()
/* only CHECK returned value from SDstart if the failure wasn't
because of "too many open files" */
else
- CHECK(fids[index], FAIL, "test_maxopenfiles: SDstart");
+ CHECK(fids[index], FAIL, "test_max_open_files: SDstart");
}
/* Close all the files, then try opening all again to verify their
names, this is to test bugzilla 440 */
for (index = 0; index < temp_limit; index++) {
status = SDend(fids[index]);
- CHECK(status, FAIL, "test_maxopenfiles: SDend");
+ CHECK(status, FAIL, "test_max_open_files: SDend");
fids[index] = SDstart(filename[index], DFACC_RDWR);
- CHECK(fids[index], FAIL, "test_maxopenfiles: SDstart");
+ CHECK(fids[index], FAIL, "test_max_open_files: SDstart");
}
/* Verify their names */
for (index = 0; index < temp_limit; index++) {
status = SDgetfilename(fids[index], readfname);
- CHECK(status, FAIL, "test_maxopenfiles: SDgetfilename");
+ CHECK(status, FAIL, "test_max_open_files: SDgetfilename");
/* Verify the file name retrieved against the original */
if (strcmp(readfname, filename[index])) {
@@ -296,7 +296,7 @@ test_max_open_files()
/* Close then remove all the files */
for (index = 0; index < temp_limit; index++) {
status = SDend(fids[index]);
- CHECK(status, FAIL, "test_maxopenfiles: SDend");
+ CHECK(status, FAIL, "test_max_open_files: SDend");
remove(filename[index]);
}
=====================================
release_notes/INSTALL
=====================================
@@ -16,11 +16,10 @@ CONTENTS
--------
1. Obtaining HDF4
2. Third-party Software Requirements
- 3. Optional Szip Compression Library
- 4. HDF4 Source Code and Precompiled Binaries
- 5. Build and Install HDF4 C and Fortran Libraries and tools with CMake
-
-
+ 2.1. Optional Szip Compression Library
+ 3. HDF4 Source Code and Precompiled Binaries
+ 3.1. Build and Install HDF4 C and Fortran Libraries and tools with CMake
+ 4. Quick Start Presets
*****************************************************************************
@@ -34,16 +33,53 @@ CONTENTS
ZLIB 1.1.4 or later. The software can be downloaded from: "https://github.com/madler/zlib.git"
-3. Optional Szip Compression Library
+2.1. Optional Szip Compression Library
HDF4 may be configured to use the Szip compression library. The
open source software can be downloaded from: "https://github.com/MathisRosenhauer/libaec.git"
-4. HDF4 Source Code and Precompiled Binaries
+3. HDF4 Source Code and Precompiled Binaries
The HDF Group provides source code and pre-compiled binaries from the
HDF4 github releases page:
https://github.com/HDFGroup/hdf4/releases
-5. Build and Install HDF4 C and Fortran Libraries and tools with CMake
+3.1. Build and Install HDF4 C and Fortran Libraries and tools with CMake
see the release_notes/INSTALL_CMake.txt file.
+4. Quick Start Presets
+ You want to build HDF4 with CMake or use an installed HDF4 binary with CMake,
+ but there are so many options to consider.
+
+4.1. Solution
+ CMake introduced presets in version 3.19. HDF Group provides a file in the source,
+ CMakePresets.json, requiring CMake 3.25 or higher. This file is in the HDF4 library
+ source as well as the HDF4Examples source of the installed binary.
+ The library source file will build HDF4 with the options for building a typical
+ shared library with the common languages for a platform. The features include building
+ the tools, examples, and the shared and static libraries.
+ The HDF4Examples source file will build the examples with the components that were
+ enabled by the options selected when the install HDF4 library was built. The typical
+ library built by HDF and available from the HDF4 Releases page include C, Java, and Fortran
+ compilers along with the tools, examples, and the shared and static libraries.
+
+4.2. Discussion
+ The CMakePresets.json file is located in the root directory of the HDF4 source and
+ the HDF4Examples source of the installed binary.
+ It is from here you will execute the cmake command to build HDF4. The following
+ example shows how to build HDF4 or examples with the CMakePresets.json file:
+ - change directory to the source folder
+ - execute "cmake --workflow --preset ci-StdShar-<compiler-type> --fresh"
+ where "<compiler-type>" is GNUC, MSVC, Clang
+
+ The above example will create a "build" folder in the source parent directory, which
+ will contain the results of the build, including installation package files when the
+ library is built.
+
+4.3. Customization
+ See the HDF4 documentation for more on presets, especially the presets section in:
+ - release_notes/INSTALL_CMake.txt file
+
+4.4. See Also
+ See CMake documentation for details on presets:
+ - https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html
+
=====================================
release_notes/INSTALL_CMake.txt
=====================================
@@ -7,12 +7,13 @@
Section I: Preconditions
Section II: Quick Step Building HDF4 Libraries with CMake Script Mode
Section III: Quick Step Building HDF4 Libraries with CMake Command Mode
-Section IV: Further considerations
-Section V: Options for building HDF4 Libraries with CMake command line
+Section IV: Further Considerations
+Section V: Options for building HDF4 Libraries with CMake Command Line
Section VI: CMake option defaults for HDF4
Section VII: User Defined Options for HDF4 Libraries with CMake
-Section VIII: Using CMakePresets.json for compiling
-Section IX: Autotools Configuration and Build
+Section VIII: Using CMakePresets.json for Compiling
+Section IX: Using the Library
+Section X: Autotools Configuration and Build
************************************************************************
@@ -35,7 +36,7 @@ CMake version
1. We suggest you obtain the latest CMake from the Kitware web site.
The HDF 4.3"X" product requires a minimum CMake version 3.18,
where "X" is the current HDF4 release version. If you are using
- VS2022, the minimum version is 3.21.
+ VS2022, the minimum version is 3.21. CMakePresets requires CMake 3.25.
Note:
To change the install prefix from the platform defaults initialize
@@ -50,18 +51,25 @@ This short set of instructions is written for users who want to quickly
build the HDF4 C and Fortran shared libraries and tools
from the HDF4 source code package using the CMake tools. This procedure
will use the default settings in the config/cmake/cacheinit.cmake file.
-HDF Group recommends using the ctest script mode to build HDF4.
+The HDF Group recommends using the presets process to build HDF4.
+
+NOTE: if you are using CMake 3.25 or later, you can use the presets process.
+ The CMakePresets.json file in the source directory will configure, build, test,
+ and package HDF4 with the same options that are set in the cacheinit.cmake file.
+ In addition, it will get the optional files listed below that are needed, from
+ the appropriate repositories.
+ See Section VIII: Using CMakePresets.json for compiling
-------------------------------------------------------------------------
-------------------------------------------------------------------------
Individual files needed as mentioned in this document
-------------------------------------------------------------------------
CMake build script from https://github.com/HDFGroup/hdf4/tree/master/config/cmake/scripts:
- CTestScript.cmake
+ CTestScript.cmake -- CMake build script
Configuration files from https://github.com/HDFGroup/hdf4/tree/master/config/cmake/scripts:
- HDF4config.cmake
- HDF4options.cmake
+ HDF4config.cmake -- CMake configuration script
+ HDF4options.cmake -- CMake configuration options script
External compression szip, jpeg, and zlib libraries:
JPEG "https://www.ijg.org/filesz"/jpegsrc.v9e.tar.gz"
@@ -272,12 +280,13 @@ Notes: This short set of instructions is written for users who want to
========================================================================
-IV. Further considerations
+IV. Further Considerations
========================================================================
1. We suggest you obtain the latest CMake for windows from the Kitware
web site. The HDF 4.3"X" product requires a minimum CMake version 3.18.
- If you are using VS2022, the CMake minimum version is 3.21.
+ If you are using VS2022, the CMake minimum version is 3.21. CMakePresets
+ requires CMake 3.25.
2. HDF4 requires Zlib and JPEG. Szip (aka libaec) is optional:
A. Download the binary packages and install them in a central location.
@@ -410,16 +419,12 @@ IV. Further considerations
Notes: CMake and HDF4
- 1. Using CMake for building and using HDF4 is under active development.
- We have attempted to provide error-free files. The CMake specific
- files may change before the next release.
-
- 2. CMake support for HDF4 development should be usable on any
+ 1. CMake support for HDF4 development should be usable on any
system where CMake is supported. Please send us any comments on
how CMake support can be improved on any system. Visit the
Kitware site for more information about CMake.
- 3. Build and test results can be submitted to our CDash server:
+ 2. Build and test results can be submitted to our CDash server:
The CDash server for community submissions of hdf is at
https://my.cdash.org.
@@ -431,7 +436,7 @@ Notes: CMake and HDF4
configuration every time. "EXPERIMENTAL" submissions can be expected to
be different for each submission.
- 4. See the appendix at the bottom of this file for examples of using
+ 3. See the appendix at the bottom of this file for examples of using
a ctest script for building and testing. Using a ctest script is
preferred because of its flexibility.
@@ -444,6 +449,15 @@ Notes: CMake in General
available for the configuration step. The steps are similar for
all the operating systems supported by CMake.
+ 3. Setting the installation location from the command line at configure time
+ a. Using the --install-prefix command line option, which is available since
+ CMake version 3.21:
+ cmake --install-prefix /my/folder/to/install/to ..
+ b. Using -DCMAKE_INSTALL_PREFIX :
+ cmake -DCMAKE_INSTALL_PREFIX=/my/folder/to/install/to ..
+ c. Using the CMAKE_INSTALL_PREFIX environment variable, which is available
+ since CMake version 3.29:
+ CMAKE_INSTALL_PREFIX=/my/folder/to/install/to cmake ..
========================================================================
V. Options for Building HDF4 Libraries with the CMake Command Line
@@ -467,6 +481,11 @@ These five steps are described in detail below.
available in your Start menu. For Linux, UNIX, and Mac users the
executable is named "cmake-gui" and can be found where CMake was
installed.
+ Another option is to use the presets file, CMakePresets.json, to configure,
+ build, test, and package HDF4. See section VIII: Using CMakePresets.json for compiling
+ for use of that file. You can create a CMakeUserPresets.json file to create a
+ specific configuration for your environment. Note that Visual Studio and XCode can
+ use the presets files.
Specify the source and build directories.
@@ -489,22 +508,32 @@ These five steps are described in detail below.
* MinGW Makefiles
* NMake Makefiles
* Unix Makefiles
- * Visual Studio 14 2015
- * Visual Studio 14 2015 Win64
+ * Ninja
* Visual Studio 15 2017
* Visual Studio 15 2017 Win64
* Visual Studio 16 2019
* Visual Studio 17 2022
<options> is:
- * SZIP_INCLUDE_DIR:PATH=<path to szip includes directory>
- * SZIP_LIBRARY:FILEPATH=<path to szip/library file>
- * libaec_INCLUDE_DIR:PATH=<path to libaec includes directory>
- * libaec_LIBRARY:FILEPATH=<path to libaec/library file>
- * ZLIB_INCLUDE_DIR:PATH=<path to zlib includes directory>
- * ZLIB_LIBRARY:FILEPATH=<path to zlib/library file>
- * JPEG_INCLUDE_DIR:PATH=<path to jpeg includes directory>
- * JPEG_LIBRARY:FILEPATH=<path to jpeg/library file>
+ For installed SZIP/libaec:
+ * SZIP_INCLUDE_DIR:PATH=<path to szip includes directory>
+ * SZIP_LIBRARY:FILEPATH=<path to szip/library file>
+ * libaec_INCLUDE_DIR:PATH=<path to libaec includes directory>
+ * libaec_LIBRARY:FILEPATH=<path to libaec/library file>
+ or
+ * SZIP_ROOT:PATH=<path to szip root directory>
+ * libaec_ROOT:PATH=<path to libaec root directory>
+ For installed ZLIB/ZLIBNG:
+ * ZLIB_INCLUDE_DIR:PATH=<path to zlib includes directory>
+ * ZLIB_LIBRARY:FILEPATH=<path to zlib/library file>
+ or
+ * ZLIB_ROOT:PATH=<path to zlib root directory>
+ For installed JPEG:
+ * JPEG_INCLUDE_DIR:PATH=<path to jpeg includes directory>
+ * JPEG_LIBRARY:FILEPATH=<path to jpeg/library file>
+ or
+ * JPEG_ROOT:PATH=<path to jpeg root directory>
+
* <HDF4OPTION>:BOOL=[ON | OFF]
<cacheinit.cmake> is:
@@ -697,7 +726,7 @@ VI. CMake Option Defaults for HDF4
In the options listed below, there are three columns of information:
Option Name, Option Description, and Option Default.
-The config/cmake/cacheinit.cmake file can override the following values.
+The config/cmake/cacheinit.cmake or CMakePresets.json file can override the following values.
---------------- General Build Options -------------------------------------
BUILD_SHARED_LIBS "Build Shared Libraries" ON
@@ -802,7 +831,7 @@ Then enable the option to the CMake configuration, build and test process.
========================================================================
-VIII: Using CMakePresets.json for compiling
+VIII: Using CMakePresets.json for Compiling
========================================================================
One problem that CMake users often face is sharing settings with other people for common
@@ -887,9 +916,50 @@ For instance, to change the support files to use a local directory, edit CMakeUs
Then you can change or add options for your specific case.
+========================================================================
+IX. Using the Library
+========================================================================
+ For information on using HDF4 see the documentation, tutorials and examples
+ found here:
+
+ https://support.hdfgroup.org/documentation/index.html
+
+ A summary of the features included in the built HDF4 installation can be found
+ in the libhdf4.settings file in the same directory as the static and/or
+ shared HDF5 libraries. However CMake provides a programmable method to
+ determine the features of the library. The CMake installation will
+ provide a CMake package configuration file, located in the installation folder,
+ cmake/hdf4-config.cmake, and can be used to determine the features of the library.
+ The file is accessed by using the find_package command in your CMakeLists.txt file.
+
+ 1. Set the HDF5_ROOT CMake variable, -DHDF4_ROOT=<install_path>
+ or environment variable, set(ENV{HDF4_ROOT} "<install_path>")
+ to the installed location of HDF4.
+ On Windows:
+ HDF4_ROOT=C:/Program Files/HDF_Group/HDF4/z.y.x/
+ On unix:
+ HDF4_ROOT=<install root folder>/HDF_Group/HDF4/z.y.x/
+
+ If you are using shared libraries, you may need to add to the path
+ environment variable. Set the path environment variable to the
+ installed location of the library files for HDF4.
+ On Windows (*.dll):
+ PATH=%PATH%;C:/Program Files/HDF_Group/HDF4/z.y.x/bin
+ On unix (*.so):
+ LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<install root folder>/HDF_Group/HDF4/z.y.x/lib
+
+ (Note there are no quote characters used on Windows and all platforms
+ use forward slashes)
+
+ 2. Add the following to your CMakeLists.txt file:
+ find_package (HDF4 NAMES hdf4 COMPONENTS C shared)
+
+ The components are optional and can be omitted if not needed. The
+ components are: shared, static, C, Fortran, Java and Tools.
+
========================================================================
-III. Autotools Configuration and Build
+X. Autotools Configuration and Build
========================================================================
See RELEASE.txt in the release_notes/ directory for the list of platforms
tested for this release.
=====================================
release_notes/RELEASE.txt
=====================================
@@ -1,4 +1,4 @@
-HDF version 4.3.1-1 currently under development
+HDF version 4.3.1 released on 2025-06-30
====================================================
INTRODUCTION
@@ -10,7 +10,7 @@ previous releases of HDF and wish to migrate to this version of HDF.
Note that the HDF4 documentation will be updated at the time of
each final release and can be found on the HDF4 support page at:
- https://portal.hdfgroup.org/display/HDF4/HDF4
+ https://portal.hdfgroup.org/display/HDF4
The official HDF4 releases can be obtained from:
@@ -28,7 +28,6 @@ CONTENTS
- Bugs fixed since HDF 4.3.0
-- Configuration
-- Library
- -- Utilities
- Documentation
- Platforms Tested
- Known problems
@@ -38,11 +37,22 @@ New features and changes
========================
Configuration:
-------------
+ None
+
+ C Library:
+ -------------
+ None
Bugs fixed since HDF 4.3.0
===========================
+ Configuration:
+ -------------
+ None
+
+ Library:
+ -------
- Fixed various uninitialized memory occurrences
Valgrind reported
@@ -73,6 +83,14 @@ Bugs fixed since HDF 4.3.0
Addresses GH-825
+ Utilities:
+ ---------
+ - Fixed hdp to display variables with rank = 0 properly
+
+ Previously the tool did not handle variables with rank = 0 correctly.
+ Thus, it simply skipped printing these variables.
+
+ Addresses HDFFR-1293
Documentation
=====================================
release_notes/USING_CMake_Examples.txt
=====================================
@@ -12,8 +12,14 @@ Notes: This short instruction is written for users who want to quickly
More information about using CMake can be found at the Kitware
site, www.cmake.org.
- CMake uses the command line and these instructions use the script
- method of the ctest command.
+ Table of Contents
+
+Section I: Preconditions
+Section II: Building HDF4 Examples with CMake
+ 1. Using presets
+ 2. Using CTestScript.cmake
+Section III: Defaults in the CMakePresets.json file
+Section IV: Defaults in the HDF4_Examples_options.cmake file
========================================================================
@@ -23,25 +29,69 @@ I. Preconditions
1. We suggest you obtain the latest CMake for your platform from the Kitware
web site. The HDF 4.3.x product requires a minimum CMake version
of 3.18. If you are using VS2022, the minimum CMake version is 3.21.
+ CMakePresets.json, requires CMake 3.25 or higher.
2. You have installed the HDF4 library built with CMake, by executing
the HDF Install Utility (the *.msi file in the binary package for
Windows or the *.sh on Linux). You can obtain pre-built binaries
from The HDF Group's website at www.hdfgroup.org.
-
+ 3. Set the HDF4_ROOT CMake variable, -DHDF4_ROOT=<install_path>
+ or environment variable, set(ENV{HDF4_ROOT} "<install_path>")
+ to the installed location of HDF4.
+ On Windows:
+ HDF4_ROOT=C:/Program Files/HDF_Group/HDF4/z.y.x/
+ On unix:
+ HDF4_ROOT=<install root folder>/HDF_Group/HDF4/z.y.x/
+
+ If you are using shared libraries, you may need to add to the path
+ environment variable. Set the path environment variable to the
+ installed location of the library files for HDF4.
+ On Windows (*.dll):
+ PATH=%PATH%;C:/Program Files/HDF_Group/HDF4/z.y.x/bin
+ On unix (*.so):
+ LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<install root folder>/HDF_Group/HDF4/z.y.x/lib
+
+ (Note there are no quote characters used on Windows and all platforms
+ use forward slashes)
========================================================================
II. Building HDF4 Examples with CMake
========================================================================
-Files in the HDF4 install directory:
+ 1. Using presets
+ Files in the HDF4 install/HDF5Examples directory:
+ CMakePresets.json
+
+ Default build process:
+ Create a directory to run the examples, i.e. \test_hdf4.
+ Copy the HDF4Examples folder to this directory.
+ Change into the HDF4Examples directory where CMakePresets.json exists.
+
+ Other options can be changed by creating a
+ CMakeUsersPresets.json file. (Advanced usage)
+
+ Available configurations presets can be displayed by executing:
+ cmake -S <path-to-source> --list-presets
+
+ Using individual command presets (where <compiler-type> is GNUC or MSVC or Clang):
+ cmake --preset ci-StdShar-<compiler-type>
+ cmake --build --preset ci-StdShar-<compiler-type>
+ ctest --preset ci-StdShar-<compiler-type>
+ cpack --preset ci-StdShar-<compiler-type>
+
+ Using the workflow preset to configure, build, and testthe standard configuration:
+ execute "cmake --workflow --preset ci-StdShar-<compiler-type> --fresh"
+ where <compiler-type> is GNUC or MSVC or Clang
+
+ 2. Using CTestScript.cmake
+ Files in the HDF4 install directory:
HDF4Examples folder
CTestScript.cmake
HDF4_Examples.cmake
HDF4_Examples_options.cmake
-Default installation process:
+ Default build process:
Create a directory to run the examples, i.e. \test_hdf4.
Copy HDF4Examples folder to this directory.
Copy CTestScript.cmake to this directory.
@@ -68,9 +118,9 @@ Default installation process:
HDF4_Examples_options.cmake file.
If the defaults are okay, execute from this directory:
- ctest -S HDF4_Examples.cmake -C Release -V -O test.log
+ ctest -S HDF4_Examples.cmake -C Release -VV -O test.log
If the defaults need change, execute from this directory:
- ctest -S HDF4_Examples.cmake,CTEST_SOURCE_NAME=MyExamples,INSTALLDIR=MyLocation -C Release -V -O test.log
+ ctest -S HDF4_Examples.cmake,CTEST_SOURCE_NAME=MyExamples,INSTALLDIR=MyLocation -C Release -VV -O test.log
When executed, the ctest script will save the results to the log file, test.log, as
indicated by the ctest command. If you wish to see more build and test information,
@@ -79,13 +129,31 @@ Default installation process:
========================================================================
-III. Defaults in the HDF4_Examples_options.cmake file
+III. Defaults in the CMakeUsersPresets.json file
+========================================================================
+
+#### DEFAULT:
+#### "generator": "Ninja"
+#### "binaryDir": "${sourceParentDir}/build/${presetName}"
+#### "name": "ci-StdShar"
+#### "BUILD_SHARED_LIBS": "ON",
+#### "USE_SHARED_LIBS": "ON"
+#### "CMAKE_BUILD_TYPE": "RelWithDebInfo"
+#### "H4EX_BUILD_FORTRAN": "OFF"
+#### "H4EX_BUILD_JAVA": "ON"
+#### "HDF4_NAMESPACE": {"type": "STRING", "value": "hdf4::"},
+#### "HDF4_PACKAGE_NAME": {"type": "STRING", "value": "hdf4"},
+#### "H4EX_BUILD_TESTING": "ON"
+
+
+========================================================================
+IV. Defaults in the HDF4_Examples_options.cmake file
========================================================================
-#### DEFAULT: ###
-#### BUILD_SHARED_LIBS:BOOL=OFF ###
-#### H4EX_BUILD_C:BOOL=ON ###
-#### H4EX_BUILD_FORTRAN:BOOL=OFF ###
-#### H4EX_BUILD_JAVA:BOOL=OFF ###
-#### H4EX_BUILD_TESTING:BOOL=OFF ###
+#### DEFAULT:
+#### BUILD_SHARED_LIBS:BOOL=OFF
+#### H4EX_BUILD_C:BOOL=ON
+#### H4EX_BUILD_FORTRAN:BOOL=OFF
+#### H4EX_BUILD_JAVA:BOOL=OFF
+#### H4EX_BUILD_TESTING:BOOL=OFF
=====================================
release_notes/USING_HDF4_CMake.txt
=====================================
@@ -15,21 +15,15 @@ Notes: This short instruction is written for users who want to quickly
all of the operating systems supported by CMake.
NOTES:
- 1. Using CMake for building and using HDF4 is under active
- development. While we have attempted to provide error-free
- files, please understand that development with CMake has not
- been extensively tested outside of HDF. The CMake specific
- files may change before the next release.
-
- 2. CMake for HDF4 development should be usable on any system
+ 1. CMake for HDF4 development should be usable on any system
where CMake is supported. Please send us any comments on how
CMake support can be improved on any system.
- 3. See the appendix at the bottom of this file for an example
+ 2. See the appendix at the bottom of this file for an example
of using a ctest script for building and testing. See
INSTALL_CMake.txt for more information.
- 4. See https://cmake.org/cmake/help/latest/command/find_package.html
+ 3. See https://cmake.org/cmake/help/latest/command/find_package.html
for more information on the CMake "Config Mode Search Procedure".
@@ -40,6 +34,7 @@ I. Preconditions
1. We suggest you obtain the latest CMake for your platform from the Kitware
web site. The HDF 4.3.x product requires a minimum CMake version
of 3.18. If you are using VS2022, the minimum CMake version is 3.21.
+ CMakePresets.json, requires CMake 3.25 or higher.
2. You have installed the HDF4 library built with CMake, by executing
the HDF Install Utility (the *.msi file in the binary package for
View it on GitLab: https://salsa.debian.org/debian-gis-team/hdf4/-/compare/04645ba225db5256c800e7917e4ed4f91d430ef3...20a1ef8aa2507cbe230797652019a591e73c130e
--
View it on GitLab: https://salsa.debian.org/debian-gis-team/hdf4/-/compare/04645ba225db5256c800e7917e4ed4f91d430ef3...20a1ef8aa2507cbe230797652019a591e73c130e
You're receiving this email because of your account on salsa.debian.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-grass-devel/attachments/20250701/67a47160/attachment-0001.htm>
More information about the Pkg-grass-devel
mailing list