Changes in Framework Linking from 10.4 to 10.5
Changes in Framework Linking from 10.4 to 10.5
- Subject: Changes in Framework Linking from 10.4 to 10.5
- From: Clark Goble <email@hidden>
- Date: Wed, 19 Nov 2008 13:07:38 -0700
Hi. I have a framework that folks have successfully linked against for years. My clients just recently changed their application to link against 10.5 rather than 10.4. As soon as they do this when they call my framework's functions they get a error of this sort:
Program received signal: “EXC_BAD_ACCESS”.
I rebuilt my framework with XCode 3.1.1 and linked against 10.5 SDK rather than 10.4 but it doesn't appear to make any difference. Did something change? My client (a rather large software package used probably by everyone here) loads the framework using some modified sample code from Apple. (i.e. CFBundleGetMainBundle, CFBundleCopyPrivateFrameworksURL, CFBundleCreate and CFBundleLoadExecutable)
All the setup of the framework goes without triggering any errors. It's just that first function call that doesn't work.
Clark Goble Lextek International
(801) 655-1994
|
_______________________________________________
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