Embedded private frameworks
Embedded private frameworks
- Subject: Embedded private frameworks
- From: Quincey Morris <email@hidden>
- Date: Fri, 01 Apr 2011 00:14:50 -0700
I think I've figured out everything I needed to do to embed private frameworks in an application bundle. (This is the first time I've tried, and the process isn't documented completely and accurately anywhere that I could find. The Frameworks Programming Guide [http://developer.apple.com/library/mac/#documentation/MacOSX/Conceptual/BPFrameworks/Tasks/CreatingFrameworks.html] was last updated in 2007. In retrospect, it kind of makes sense, but it wasn't a lot of use when I didn't know what I was doing. This is for Xcode 4, which has the extra complication of being clever enough to figure out how to make your application use the correct frameworks -- even when the build settings are mis-configured -- if the frameworks are included in the application's workspace. That cleverness hid a lot of sins that don't show up till I tried to build an archive.)
Anyway, the release application bundle looks correct, but I get the following warning during the archive process, once for each of the embedded frameworks during its own target build:
> Warning: Installation Directory starts with @executable_path but Skip Install is disabled.
The installation directory build setting is indeed "@executable_path/../Frameworks", and Skip Install is indeed 'No', so perhaps all I need to do is change Skip Install to 'Yes'. But I'm worried that the warning indicates there's something significant I got wrong. The descriptions of the settings don't give any clue as to why they're related, or why Skip Install would need to be 'Yes' -- or why Skip Install *doesn't* seem intended to skip installation when 'Yes'.
What's the correct solution?
_______________________________________________
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