Re: Weak linking framework with bundle ?
Re: Weak linking framework with bundle ?
- Subject: Re: Weak linking framework with bundle ?
- From: Eric Albert <email@hidden>
- Date: Fri, 5 Nov 2004 01:33:23 -0800
On Nov 5, 2004, at 1:21 AM, Mike Richmond wrote:
At 9:34 am -0800 4/11/04, Eric Albert wrote:
Actually, <http://developer.apple.com/technotes/tn2002/tn2064.html>
says "It is highly recommended that you use the December 2002 toolset
if you want to use weak linking and the Availability Macros."
If this is meant to be read as "don't try this with GCC 2.95.2" then I
suggest it needs rewording. I've read this tech note many times and
never interpreted it in that way.
I don't know whether it's meant to be read that way. I do know that
GCC 2.95.2 is very, very old, and new compiler features generally
aren't backported to old versions. You really shouldn't be using GCC
2.95.2 unless you absolutely have to (and if you do, I'd be idly
curious to know why).
I'd strongly suggest using GCC 3.1 (or, better yet, 3.3) instead.
(For that matter, 3.1 and 3.3 are much better than 2.95.2 for many
other reasons. You shouldn't have a need for 2.95.2 at all.)
Yes, I hear that, but I've seen nothing to suggest that weak linking
is not supported by 2.95.2, and it certainly works in some cases.
Should I be able to weak link a framework to a bundle at all (I assume
so as the tools let me try)? With 3.3? With 3.1? With 2.95.2?
The December 2002 tools included GCC 3.1 as the default compiler. That
or any subsequent compiler release should work. I can't speak for your
specific scenario -- I don't know anything about weak linking -- but
the technote probably means that it works with the default compiler in
that release. Maybe it's supposed to work with 2.95.2, but since it
doesn't seem to be working for you your best bet is to try a newer,
better compiler version.
-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