Re: linking a static library, not a dylib
Re: linking a static library, not a dylib
- Subject: Re: linking a static library, not a dylib
- From: "Justin C. Walker" <email@hidden>
- Date: Tue, 10 Oct 2006 15:12:24 -0700
On Oct 10, 2006, at 15:06 , Eric Albert wrote:
On Oct 10, 2006, at 2:52 PM, Justin C. Walker 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.
You can also use the -search_paths_first linker flag. See the ld
man page for details.
Good point; using this means you use the first option above (.dylib
and .a in separate directories).
Justin
--
Justin C. Walker, Curmudgeon-At-Large
Director
Institute for the Enhancement of the Director's Income
--------
"Weaseling out of things is what separates us from the animals.
Well, except the weasel."
- Homer J Simpson
--------
_______________________________________________
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