Fwd: Beginner question -- how to resolve dependent dylib's when linking

[William Davis]

possible useful  info from uni-porting list;

Begin forwarded message:

> From: Martin Costabel <costabel at wanadoo.fr>
> Date: December 30, 2007 8:12:57 AM EST
> To: kelsey at slac.stanford.edu
> Cc: unix-porting at lists.apple.com
> Subject: Re: Beginner question -- how to resolve dependent dylib's  
> when	linking
>
> Peter O'Gorman wrote:
>> Mike Kelsey wrote:
>>> Is there an option I can give to |libtool| or/and |ld|, such that  
>>> dependent
>>> libraries mentioned inside .dylib's will be resolved via the -L  
>>> options?
>> See -dylib_file in the ld(1) manpage.
>
> If you are on Leopard, you probably don't have to do anything in  
> this case. It is standard behavior there (in most situations  
> perceived as an annoying bug, though) that indirect libraries are  
> *not* looked up according to their install_name, but in the  
> directories defined by -L.
>
> Perversely, you are forced to use -dylib_file, or explicit -L -l  
> references, if you want them to be looked up at the path mentioned  
> in the referencing dylib. This wreaks all kinds of havoc if you have  
> several dylibs of the same name on your system, but in your  
> situation this may be the behavior you are wishing for.
>
> -- 
> Martin
>
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Unix-porting mailing list      (Unix-porting at lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/unix-porting/frstan%40bellsouth.net
>
> This email sent to frstan at bellsouth.net



William Davis
frstanATbellsouthDOTnet
Mac OS X.5.1 Darwin 9.1.0
X11.app 2.1.1 - (xorg-server 1.3.0-apple5)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/macports-dev/attachments/20080107/59c87b45/attachment-0001.html