Re: Linking behavior for dylibs without the lib prefix
Re: Linking behavior for dylibs without the lib prefix
- Subject: Re: Linking behavior for dylibs without the lib prefix
- From: Eric Albert <email@hidden>
- Date: Wed, 11 Jan 2006 11:42:12 -0800
On Jan 11, 2006, at 10:41 AM, Gabriele de Simone wrote:
There's been lots of (useful) talk on dynamic libraries, but there is
one issue I have personally been unable to understand from the docs or
from this list.
How is linking against a dynamic library that does not have the
canonical "lib" prefix any different than linking against one with
the proper name?
So far, I have collected the following info: the library is not linked
via the -l<someLibrary> argument, and the full path to the library is
passed in.
Does linking work the same even if the library is not specified as
part of a -l argument?
Yes. As far as the linker's concerned, no matter how you've specified
a library everything's the same.
And if the dylib is not linked via the -l argument, does the "Library
Search Paths" build setting (-L) still have any effect?
I'm not sure, but I suspect not. I'm afraid I don't know what Xcode
does for this case today, but it should pass the full path to the
library to the linker. Then -L wouldn't matter, but the library you've
added to the project would be the one linked in.
-Eric
_______________________________________________
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