Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: static libraries

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:
http://lists.apple.com/mailman/options/xcode-users/email@hidden

This email sent to email@hidden


Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.