Re: Getting a private header that is in the .app to run instead of the standard version
Re: Getting a private header that is in the .app to run instead of the standard version
- Subject: Re: Getting a private header that is in the .app to run instead of the standard version
- From: Quincey Morris <email@hidden>
- Date: Fri, 18 Nov 2011 22:14:35 -0800
On Nov 18, 2011, at 22:05 , Tarek Khouzam wrote: I have a PrivateFramework that gets copied durning the build phase into Contents/Frameworks. I just can't get the app to load that version. It loads the version that is in /System/Library/PrivateFramework. Is there something I need to change in the build settings to run my version of the framework.
If you haven't done so already, change the "Installation Directory" build setting (in the "Deployment" section of the settings for the framework target) to:
@executable_path/../Frameworks
You should probably also set "Skip Install" to "Yes" -- at least in the original Xcode 4 release there was a spurious but harmless build error if you left it to default to "No".
|
_______________________________________________
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