Re: static to override dylib
Re: static to override dylib
- Subject: Re: static to override dylib
- From: "R.L. Grigg" <email@hidden>
- Date: Mon, 14 Jul 2008 11:38:51 -0700
Just thinking out loud... Wouldn't it make sense that if you
explicitly include libxyz.a that this would tell the linker that you
do not want to link against libxyz.dylib? This would sure simplify
things and save a lot of headaches.
Russ
On Jul 14, 2008, at 8:40 AM, Peter O'Gorman wrote:
Jake wrote:
What is the recommended approach to configure Xcode to link in a
static library that overrides the dylib one in /usr/lib?
Unless you add the -search_paths_first linker flag (I am sure there is
an Xcode checkbox for this somewhere, but do not currently have access
to my mac to check), the linker will search along all -L paths and
system search paths looking for a shared version of libiconv before
going back to the start and looking for a static archive.
Check the build transcript to ensure that either your libiconv.a
archive
is listed with its full path or -search_paths_first appears along with
the -L/path/to/static/archive/ -liconv.
_______________________________________________
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