Since Xcode 3.0, ld insists on linking CoreData.framework
Since Xcode 3.0, ld insists on linking CoreData.framework
- Subject: Since Xcode 3.0, ld insists on linking CoreData.framework
- From: Jerry Krinock <email@hidden>
- Date: Thu, 6 Dec 2007 08:15:46 -0800
I have a Cocoa application project:
Basic SDK Path = /Developer/SDKs/MacOSX10.4u.sdk
MAC_OSX_DEPLOYMENT_TARGET_i386 = 10.4
MAC_OSX_DEPLOYMENT_TARGET_ppc = 10.3
Features requiring Mac OS 10.4 API are compiled in a separate bundle
and loaded programatically.
Everything was working fine before I started building with Xcode 3.0.
Now, when I run otool -l on the product's executable, I get, at the end:
Load command 27
cmd LC_LOAD_DYLIB
cmdsize 92
name /System/Library/Frameworks/CoreData.framework/Versions/
A/CoreData (offset 24)
time stamp 2 Wed Dec 31 16:00:02 1969
current version 92.1.0
compatibility version 1.0.0
which causes it to not launch when run in 10.3.9. (Actually, many
things are different when I compare the new otool -l report with the
old one from my Xcode 2.5-built project. There are also new Load
commands for "AppKit" and "ApplicationServices".)
Looking carefully through Groups & Files, I noticed that Core Data was
a linked framework. I don't remember putting it there, but I removed
it, cleaned, and rebuilt. Still the same problem.
The only reference to my "Tiger stuff" bundle in Groups & Files is in
"Referenced Projects". It is also a dependency.
In Xcode 3.0 release notes, I read:
Support for building for Mac OS X 10.3.9 is disabled by default. To
enable this support, click Custom Install and check on the "Mac OS X
10.3.9 Support" in the Installer.
I believe I did check this while installing. Is there any way to
verify?
What, in general, triggers ld to write a Load command in the executable?
Thanks,
Jerry Krinock
_______________________________________________
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