Re: Problem running on 10.3 when building with Xcode 3.0: NSAffineTransform not found in Foundation
Re: Problem running on 10.3 when building with Xcode 3.0: NSAffineTransform not found in Foundation
- Subject: Re: Problem running on 10.3 when building with Xcode 3.0: NSAffineTransform not found in Foundation
- From: Scott Tooker <email@hidden>
- Date: Thu, 20 Dec 2007 11:46:58 -0800
On Dec 20, 2007, at 9:00 AM, Chris Espinosa wrote:
On Dec 20, 2007, at 2:40 AM, Chris Suter wrote:
I've got a problem running on 10.3 where it's failing to run
because it complains that NSAffineTransform cannot be found by dyld
(it's expecting to find it in Foundation). On 10.3
NSAffineTransform is actually in AppKit so it has a fair point, but
it was working fine when I built it with earlier versions of Xcode.
I'm guessing it used to work fine because the symbol was being
lazily bound (presumably it doesn't mind that the symbol is in
AppKit rather than Foundation when lazily binding). The Leopard
linker, for some reason, isn't marking the symbol to be lazily
bound. That's the only difference I've found so far.
Can anyone offer me some help with this? I'm looking for a
workaround. I haven't filed a bug yet but I will do tomorrow.
In earlier versions of Xcode, the default for Mac OS X Deployment
Target was something absurdly low like 10.1 or 10.2. In Leopard
it's the current system, which is 10.5. So projects that previously
built without an explicit Mac OS X Deployment Target setting would
have worked on 10.3 but now won't, and you need to explicitly set
that value in the target's build settings.
Actually it was worse in Xcode 2.x and earlier. For PowerPC (32-bit)
the default was 10.1, for Intel (32-bit) it was 10.4, and for 64-bit
PowerPC it was 10.4 (in essence, you had to remember which version of
Mac OS X introduced support for a given architecture). In Xcode 3, gcc
changed its behavior to be much simpler and in line with gcc behavior
on other UNIX platforms, by default gcc will always target the version
of Mac OS X that it is building on.
In Xcode 3.0, we also added support for the SDK to provide a default
value for Mac OS X Deployment Target (so if you are using the Mac OS X
10.4u SDK, Mac OS X Deployment Target should default to 10.4 unless
you have overriden the value at the project or target level) to lessen
the impact of this change in gcc.
Scott
Chris
_______________________________________________
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
_______________________________________________
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