On 31/01/2013, at 9:50 AM, Todd Heberlein <todd_heberl...@mac.com> wrote:
> Every subsequent change to my Frameworks (e.g., changing them to build for > 10.7) would update their respective Debug or Release folders in the Derived > Data, but these changes *never* got copied into the app's bundle. The older > compiled code kept getting copied back in. > > So… when embedding private frameworks into an app, do *not* check "Copy items > into destination group's folder (if needed)". That setting has no bearing on whether the framework is copied to the bundle when it is built. It only sets whether the source file is copied on disk into the local project's folder and managed from there, or whether it's left where it was and managed from there. If you are sharing code among several projects, this effectively sets whether the code becomes forked when used in another project if they don't share the same file locations on disk. The Copy Files build phase will copy files such as frameworks to the built bundle. Though Kyle suggests this is done automatically these days, I've never seen that behaviour; I always have to add embedded frameworks to this build phase. Maybe I'm a bit behind the latest Xcode (4.4.0)? --Graham _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
