CMB-Superbuild issueshttps://gitlab.kitware.com/cmb/cmb-superbuild/-/issues2024-01-03T23:12:53-05:00https://gitlab.kitware.com/cmb/cmb-superbuild/-/issues/120Linux CI runners require LD_LIBRARY_PATH due to Qt2024-01-03T23:12:53-05:00David ThompsonLinux CI runners require LD_LIBRARY_PATH due to QtThe aeva/session (and presumably other repos, hence an issue on cmb-superbuild) require the linux CI runner to have [the LD_LIBRARY_PATH set like so](https://gitlab.kitware.com/aeva/session/-/merge_requests/82/diffs#eb70bee14b9c013767235...The aeva/session (and presumably other repos, hence an issue on cmb-superbuild) require the linux CI runner to have [the LD_LIBRARY_PATH set like so](https://gitlab.kitware.com/aeva/session/-/merge_requests/82/diffs#eb70bee14b9c013767235e58e66b5583fe843077_11_11). This is because the build attempts to run qhelpgenerator and other qt programs that link to the superbuild's libbz2.so which appears to lack an rpath.Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/cmb/cmb-superbuild/-/issues/110OCCT only uses system fontconfig2023-05-18T14:04:31-04:00Ben BoeckelOCCT only uses system fontconfigThe `occt` package doesn't support custom `fontconfig` package, so it always uses the system copy. We should add `find_package(Fontconfig)` and use it instead of just assuming it is around.
See https://dev.opencascade.org/index.php?q=no...The `occt` package doesn't support custom `fontconfig` package, so it always uses the system copy. We should add `find_package(Fontconfig)` and use it instead of just assuming it is around.
See https://dev.opencascade.org/index.php?q=node/1295 for upstream collaboration here.
Cc: @ryan.krattiger1https://gitlab.kitware.com/cmb/cmb-superbuild/-/issues/42SMTK configure step does not consistently find HDF52017-05-15T20:14:02-04:00John TourtellottSMTK configure step does not consistently find HDF5When the superbuild is configuring smtk, cmake fails to consistently find HDF5. A completely new build seems to work, however, rebuilding an existing build -- even after deleting the SMTK directory -- does not.
The issues seems to be i...When the superbuild is configuring smtk, cmake fails to consistently find HDF5. A completely new build seems to work, however, rebuilding an existing build -- even after deleting the SMTK directory -- does not.
The issues seems to be in the FindHDF5_MOAB.cmake file in the thirdparty/moab/config folder. The strangeness is that when the system find_package(HDF5) call on line 14 fails, the HDF5_DIR variable gets set to $superbuild/install/share/cmake/hdf5 -- this looks like the correct directory, although it is not clear why or where that occurs. But then, on line 23 of the file, the code looks at the path ${HDF5_DIR}/share/cmake/hdf5/hdf5-config.cmake which doesn't exist. So for this code to "work", the HDF5_DIR var would need to be set to the superbuild install directory.Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/cmb/cmb-superbuild/-/issues/41Protocol "https" not supported or disabled in libcurl2017-05-15T20:14:02-04:00Neil Carlsonneil.n.carlson@gmail.comProtocol "https" not supported or disabled in libcurlI'm running into this problem on a somewhat dated Fedora 21 system when the build gets to vxl:
```
[ 29%] Performing download step (download, verify and extract) for 'vxl'
-- downloading...
src='https://github.com/judajake/vxl/arch...I'm running into this problem on a somewhat dated Fedora 21 system when the build gets to vxl:
```
[ 29%] Performing download step (download, verify and extract) for 'vxl'
-- downloading...
src='https://github.com/judajake/vxl/archive/44433e4bd8ca3eabe4e5441444bf2a050d689d45.tar.gz'
dst='/scratch/cmb-tpl/downloads/44433e4bd8ca3eabe4e5441444bf2a050d689d45.tar.gz'
timeout='none'
CMake Error at vxl-stamp/download-vxl.cmake:27 (message):
error: downloading
'https://github.com/judajake/vxl/archive/44433e4bd8ca3eabe4e5441444bf2a050d689d45.tar.gz'
failed
status_code: 1
status_string: "Unsupported protocol"
log: Protocol "https" not supported or disabled in libcurl
Closing connection -1
```
/usr/bin/curl itself has no problems with https, so I'm puzzled as to what is going on here. Suggestions?Ben BoeckelBen Boeckel