Fwd: Weak linking constants
Fwd: Weak linking constants
- Subject: Fwd: Weak linking constants
- From: Nick Zitzmann <email@hidden>
- Date: Mon, 18 Oct 2004 15:29:04 -0600
I'm not sure if my original message was distributed or not, so please
accept my apologies if you received this message twice...
Begin forwarded message:
From: Nick Zitzmann <email@hidden>
Date: October 18, 2004 12:55:14 PM MDT
To: email@hidden
Subject: Weak linking constants
On one project I'm working on I'm trying to retain backward
compatibility with Mac OS X 10.2.x, so I've set up a test system
running 10.2.8 and I've set up my project to use 10.2 as the
deployment target. Unfortunately, when I run the app on the 10.2.8
system, it always crashes when it runs into a constant that is
_supposed_ to be weak linked. Simply checking for the availability of
the constant using an if statement, as described in
<http://developer.apple.com/documentation/MacOSX/Conceptual/
BPFrameworks/Concepts/WeakLinking.html>, is what is causing the crash
to occur. If I take out the if statement, it still crashes whenever
the symbol is used.
Some details:
1. The target's deployment target is set to 10.2 with no SDK (I want
to use a handful of 10.3 symbols if they are present)
2. I've verified in the build log that "setenv
MACOSX_DEPLOYMENT_TARGET 10.2" is appearing before the linker is
called
3. I'm using Xcode 1.5 and GCC 3.3 to build the target
4. ZeroLink and F&C are disabled
5. The constant it's tripping on is supposed to be weak linked (it is
an Apple framework, and it has
"AVAILABLE_MAC_OS_X_VERSION_10_3_AND_LATER" appear on its line in the
header)
Why is this crashing, and how do I straighten this out?
Nick Zitzmann
<http://www.chronosnet.com/>
Nick Zitzmann
<
http://www.chronosnet.com/>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden