Re: [Oorexx-devel] A few questions ad CMake and libraries on Unix

Got carried away in the midst of testing a few variations of CMakeList (had to fix installations on Apple for LibreOffice - it does not have all of the standard directories of OOo anymore - and in addition Java 9 and higher on Apple for the OpenOffice/LibreOffice ooRexx scripts, if using the GUI

[Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

I finally took the time to read up on the dynamic linker on macOS. Linking the dylibs into /usr/local/lib is not the solution. (And it requires sudo/root, which we should not need for a local, portable installation.) This https://matthew-brett.github.io/docosx/mac_runtime_link.html

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

On Wed, Jan 2, 2019 at 4:15 PM René Jansen wrote: > I finally took the time to read up on the dynamic linker on macOS. Linking > the dylibs into /usr/local/lib is not the solution. (And it requires > sudo/root, which we should not need for a local, portable installation.) > This https://matthew-b

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

Dear all, please hold your horses! I have also been busy with the ooRexx installatier for MAC the last few days and I have a MUCH more positive view on it all! First of all I made a pristine installation (with a swiped disk) of the latest os, macOS Mojave, macOS 10.14.2 (18C54), Darwin 18.2.0,

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

A small remark: Erich has found out that the dyld stuff will not work since it is not inherited. A rexx program calling another rexx program (example: test cases) fail. He can put it in more technical terms I am sure, but my take on it is that this is a dead end on Darwin/macOS Hälsningar/Rega

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

Hi P.O., what Erich meant is that for some time now the *environment variable* containing the dyld library path is not inherited in subshells. We have to use dyld as that is the way shared libraries on macOS work. We have to work at making sure this environment variable is not needed anymore -

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

The discussion about the libraries is getting more and more confusing … With these settings all works fine for me without bothering To export DYLD_LIBRARY_PATH or LD_LIBRARY_PATH # do not skip the full RPATH for the build tree SET( CMAKE_SKIP_BUILD_RPATH FALSE) # when building, don't use the

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 02.01.2019 um 23:13 schrieb René Jansen : > > Hi P.O., > > what Erich meant is that for some time now the *environment variable* > containing the dyld library path is not inherited in subshells. We have to > use dyld as that is

Re: [Oorexx-devel] dynamic linking on macOS (was: Re: A few questions ad CMake and libraries on Unix)

Dear Enrico, I think you are saying the same as me - we do not need the dyld stuff for ooRexx to work, right? In my case I made no amendments to the existing CMakelist.txt, it worked out of the box. I will make an install to /opt today. Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.s