Dear all, I think there might be another way of solving this problem. If you symlink all libraries in /lib back to /bin it will look as if the libraries are in the same place as the executable ( in „." basically), so one could rely on that always being the case.
During a time when my build did not create the /lib properly all files resided in /bin. I could run all test cases using that configuration with no problems. With this convention - would it be possible to make the executables relocatable? Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 08.01.2019 um 15:46 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at>: > > Would it be possible to define RPATH such, that it always looks in the > directories ".", "./lib", > "../lib", "/usr/local/lib" (maybe even "/opt/local/lib") for the needed > libraries? > > This way a USB-stick version may have the executables in the same directory > or lib in a companion or > subdirectory. > > Currently, after a "make install" one cannot relocate the resulting binaries. > Using the binaries > from the "make" step forces one to have "lib" in a sibling directory. > > Probably with the help of > <https://gitlab.kitware.com/cmake/community/wikis/doc/cmake/RPATH-handling> > this could be solvable. > Alternatively, if one has XCode installed, one might use "install_name_tool" > to manipulate all rpath > definitions. Another alternative would be to set DYLD_LIBRARY_PATH. > > What do you think, which solution would be preferable? > > ---rony > > > > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
