[Scons-users] SCons always uses relative path even when absolute path is set with LIBPATH

[Matthew Bernard]

Hello everyone,

I submitted an issue on GitHub a couple days ago at the link below which
provides some background on my issue as well as important outputs from my
build.

Systems Notes:
Currently developing on MacOS
python version: 2.7.14
scons versions: custom scons based on 2.1.0 and 3.0.1

https://github.com/SCons/scons/issues/3128

A brief history of my problem is that I develop a code which has used scons
to compile an application for many years. Recently, we started some work
which has required us to repackage our code to be compiled as a shared
library to be linked in with another code which uses make.

I was able to modify our scripts to output the dylib files but they won't
link into the higher program because all of the dependent dylibs are
registered using relative paths. In the brief discussion that I had on
GitHub, I was told this is expected behavior which puts me in a bind
because my code is comprised of 7 projects which depend on each other to
various degrees.

I have done quite a bit of research and found that there are tools
available for linux and Mac which can postprocess the shared libraries to
reregister the shared libraries using absolute paths but I would prefer to
do this work within scons if at all possible.

Thanks for your help
Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20180525/a62216a5/attachment.html>