Re: Re: linking a static library, not a dylib
Re: Re: linking a static library, not a dylib
- Subject: Re: Re: linking a static library, not a dylib
- From: Os <email@hidden>
- Date: Tue, 10 Oct 2006 22:56:13 +0100
Thanks for the quick reply.
Is another option to somehow package the dylib with my app, so it's
available on machines that don't have it installed?
I'll have a dig through the archives, anyway.
cheers,
os.
On 10/10/06, Justin C. Walker <email@hidden> wrote:
On Oct 10, 2006, at 14:37 , Os wrote:
> How do I tell it to use the static, rather than dynamic, version of
> a lib?
This should be a FAQ; it has been discussed frequently on this list
(and the threads are in the archive).
The short answer is:
- static libraries are not really supported
- the linker will always find the .dylib before it finds
the .a
- if you have both versions, you have two choices:
- keep them in different directories and use "-L"
- specify the .a by full path name without a "-l"
You should check the archive for more detail and discussion.
Justin
--
Justin C. Walker, Curmudgeon-at-Large
() The ASCII Ribbon Campaign
/\ Help Cure HTML Email
--
email@hidden
http://www.collective.co.uk/
_______________________________________________
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