#80 Mac OS X (Lion +) and Dynamic Librarires for GDAL 3.6.x + : a need to set DYNAMIC_LIBRARY_PATH
SAGA version : 7.2.0
GDAL version : 3.6.2 (CMake built)
Softwares installation : not in /usr/local nor /Library/Frameworks or any other said "standard" locations. Almost everything in an external HD (for security purpose, and optimal developement and check)
Compiler : AppleLlvm (only working with the "old" OS X and wxWidgets up to wx v. 3.0.5, highly sensitive to the compiler name and version - Eveything failed with GCC 4.9.4, although GDAL from v. 2.2 through 3.6.2 was well compiled).
What is seen : running saga_gui, the GDAL 3.6.2 library is not found, even after having Reload all the standard libraries with SAGA. Besides, GDAL 3.6.2 CAN ONLY work with the CMake parameter GDAL_SET_INSTALL_RELATIVE_RPATH is set ON. Otherwise, running gdal_info --formats fails (no GDAL library was found).
What I did : in a Terminal window, I write : export DYNAMIC_LIBRARY_PATH=the_path_of_the_GDAL_libraries_are_installed.
Then, in the same Terminal window, I pass the saga_gui command, then Return. SAGA opens as usual, but the GDAL library was not loaded. Hence, I Reload the Libraries within SAGA, and it eventually works. GDAL 3.6.2 is OK. Raster files were loaded, and displayed, very well.
The expecting behaviour : no need to do what I did. Every dynamic library should be loaded, and work easily.
Please kindly see this :
https://gdal.org/development/building_from_source.html
NB 1. expect to buy another Mac computer with OS X at least version 10.10 (Yosemite).
2. All what is installed in a standard Mac location (e.g., /usr/local, Frameworks) obviously should work.
Kind regards,
Hi Laurent,
I think this is nothing unexpected when you install software in non-standard paths which are unknown to the system. This is all what the "DYNAMIC_LIBRARY_PATH" is for and I would suggest that you simply set this path permanently in your system (just to avoid to export it every time you want to use the software).
We are not supporting the GNU build system (automake) anymore, so we can't have a look if it would be feasible to add support for non-standard linking paths of external libraries. Hopefully this would work out of the box with recent SAGA versions which use the cmake build system (too). Note that we require more recent wxWidgets versions now, so this is currently not an option for you.
It often gets very complicated to compile/run newer software on very old OS versions that are not supported anymore. So it's nice to hear that you are able to run SAGA in this configuration on your system. Hopefully you can upgrade to a newer OS soon.
Best regards,
Volker
Solved thanks to (at least) the CMake documentation.
As soon as I have some time, I will provide you "my" doc about this. Works under MacOS Monterey (almost) 100 % securely.
Thank you !