Re: including dylibs in my .app
Re: including dylibs in my .app
- Subject: Re: including dylibs in my .app
- From: Tommy Nordgren <email@hidden>
- Date: Fri, 29 May 2009 23:52:29 +0200
On May 29, 2009, at 11:32 PM, Taylor Holliday wrote:
On Fri, May 29, 2009 at 2:17 PM, Taylor Holliday
<email@hidden> wrote:
Since I'd like to go with including the libs in my app bundle and it
seems I have to compile them myself, is there any reason why I
shouldn't just statically link them?
- Taylor
It seems like whenever there's a corresponding dylib, Xcode links to
it instead of the static lib. For example, I replaced
libportaudio.dylib with libportaudio.a in my project. However the link
command still has -lportaudio and otool still reports that I'm linked
against the dylib. Any ideas?
thanks!
- Taylor
If you link against a library libmylib.<ext> with option -lmylib, gcc
will prefer a shared lib.
If you want to link against the static version libmylib.a,
pass the full path of the library on the linker command line.
-------------------------------------
This sig is dedicated to the advancement of Nuclear Power
Tommy Nordgren
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden