Hello,

* Peter O'Gorman wrote on Thu, Sep 23, 2010 at 07:43:44AM CEST:
> On 09/22/2010 09:00 PM, Leo Davis wrote:
> >I had to patch libtool in order to get shared libraries to build with
> >the Snow Leopard '@rpath/' syntax which stands in for the place where
> >the lib gets installed.  I thought that this might be useful for more
> >than just myself.
> 
> Well, there is no method to encode @executable_path or @loader_path
> in the library install_name either. I always figured that people
> would just build as normal and then postprocess using
> install_name_tool(1) if they needed to.
> 
> Why should libtool treat the Mac OS X @rpath differently to the
> other two special paths?

More generally, $ORIGIN support (which is what a number of other linkers
call it, IIUC) should be added completely if it's added, including a
portable 'libtool' notation, testsuite coverage and fixing of fall-out,
and correct treatment of the non-absolute paths throughout ltmain.
I don't know how much work the latter would be, but guessing from the
sysroot branch, there is work to do there.

The most important question to this end is how to degrade gracefully
on systems without such a feature.

Cheers,
Ralf

Reply via email to