Re: static libraries
Re: static libraries
- Subject: Re: static libraries
- From: Bill Northcott <email@hidden>
- Date: Mon, 24 Oct 2005 09:35:09 +1000
On 24/10/2005, at 3:59 AM, Steve Checkoway wrote:
So, if ld searches in any path where ld can locate a dylib, it will
select this first - no matter what you have dragged in into your
project. Xcode just takes the canonical name and passes it to ld
(through gcc).
In order to avoid conflicts, we probably need to specify full paths
and full names. *sigh*
Yeah. =( I assume this has been filed as a bug before.
I very much doubt that Apple will regard this as a bug. Their
position on the use of static libraries is clear - somewhere between
deprecated and totally unsupported.
There are a couple of good reasons for this:
1. all the usual stuff about being able to update dynamic libraries
without needing to rebuild linked executables.
and
2. the fact that Xcode has more than one compiler which are
incompatible at the object code level. If you build a static library
with gcc-3.3 and attempt to link it with object code built with gcc-4
it will fail. The only static libraries which Apple ships are buried
in the gcc trees. So this cannot happen.
Bill Northcott
_______________________________________________
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