How to build HDF5 with libaec packaged independently? #3503

mkitti · 2023-09-04T09:48:17Z

mkitti
Sep 4, 2023

At the moment HDF5 seems configured to build libaec via a different build recipe than the one usually included with libaec:
https://github.com/HDFGroup/hdf5/blob/develop/config/cmake/LIBAEC/CMakeLists.txt

If libaec were built with its own cmake recipe, it is unclear how to built HDF5 such that it binds the produced libsz.

Answered by mkitti

I solved this issue in a cmake context by pointing libaec_DIR to the directory containing libaec-config.cmake
msys2/MINGW-packages#18328

conda-forge solved this in an autoconf context by pointing --with-szlib at the appropriate top level directory containing libsz.
https://github.com/conda-forge/hdf5-feedstock/blob/12bf852008c951d64a343a45f385f570bde7f034/recipe/build.sh#L101

I would appreciate if the need for the following cmake build processes that differ from their upstream counterparts could be documented better.
https://github.com/HDFGroup/hdf5/tree/develop/config/cmake/LIBAEC
https://github.com/HDFGroup/hdf5/blob/develop/config/cmake/ZLIB/

mkitti · 2023-09-06T23:23:05Z

I solved this issue in a cmake context by pointing libaec_DIR to the directory containing libaec-config.cmake
msys2/MINGW-packages#18328

conda-forge solved this in an autoconf context by pointing --with-szlib at the appropriate top level directory containing libsz.
https://github.com/conda-forge/hdf5-feedstock/blob/12bf852008c951d64a343a45f385f570bde7f034/recipe/build.sh#L101

I would appreciate if the need for the following cmake build processes that differ from their upstream counterparts could be documented better.
https://github.com/HDFGroup/hdf5/tree/develop/config/cmake/LIBAEC
https://github.com/HDFGroup/hdf5/blob/develop/config/cmake/ZLIB/

0 replies