Open stsp opened 2 weeks ago
It makes sense to me to support a string array as well, but you can get around this by passing the rpath as a :
delimited string, ie:
build_target(
...,
install_rpath : 'first/path:second/path:third/path'
)
This produces a very strange effect.
I did:
install_rpath: '/usr/local/i386-pc-dj64/lib64:/usr/i386-pc-dj64/lib64'
and got this:
-Wl,-rpath,/usr/local/i386-pc-dj64/lib64:XXXXXXXXXXXXXXXXXXXXXXXX -Wl,-rpath-link,/usr/local/i386-pc-dj64/lib64
So -rpath-link
ignored everything after :
and -rpath
replaced the second part with
XXX.
WTf?
Dang. Well, there goes my workaround idea.
that XXXXX thing is create padding so that at install time we can do a binary edit of the elf header instead of re-linking. It’s just breaking on the :
But not a problem, as I think hacking
around elf header is a bad idea anyway.
So lets try rpath_build
:
-Wl,-rpath,/usr/local/i386-pc-dj64/lib64:/usr/local/i386-pc-dj64/lib64:/usr/i386-pc-dj64/lib64 -Wl,-rpath-link,/usr/local/i386-pc-dj64/lib64
Not much better: -rpath
has 1 part
repeated twice, and -rpath-link
still
has just 1 part. No XXX now though.
I think there is something to fix here.
These transformations seems to make
no sense.
I have custom_target that passes a few
-Wl,-rpath=
aslink_args
. And I am getting this warning:The warning is duplicated as many times as there are
-Wl,-rpath=
args.But if I try to follow that warning, then I get:
So it seems absolutely impossible to pass multiple rpathes w/o getting multiple warnings. Please allow build_rpath and install_rpath to take the list of strings.