embedding @executable_path

[Daniel J. Luke]

On Aug 10, 2009, at 4:14 PM, acolubri wrote:
> I need all the binaries and libraries generated with macports to  
> have a
> specific path embedded into them (libtool -install_name ...). In  
> particular,
> this path has to be relative to the location of the calling  
> application
> (i.e.: @executable_path/blah/blah).

Presumably you're packaging some software that is going to use libs  
that you are using macports to build.

I've done something similar by having the build system for my .app run  
a script that runs install_name_tool on the libs I wanted to update  
(along with copying them into the app wrapper).

--
Daniel J. Luke
+========================================================+
| *---------------- dluke at geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
|   Opinions expressed are mine and do not necessarily   |
|          reflect the opinions of my employer.          |
+========================================================+



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090810/dc01f8d5/attachment.bin>