Re: Framework deployed to 'Resources' not 'Frameworks' in Contents
Re: Framework deployed to 'Resources' not 'Frameworks' in Contents
- Subject: Re: Framework deployed to 'Resources' not 'Frameworks' in Contents
- From: Graham Cox <email@hidden>
- Date: Mon, 29 Dec 2008 21:12:09 +1100
On 29 Dec 2008, at 8:26 pm, Steve Cronin wrote:
Folks;
I've got two targets built from the same project: Big and Little
Big has many resources, source files, as well as several frameworks
that are copied and then deployed to a 'Frameworks' directory in the
app file's 'Contents'.
Little has many fewer of the resources and sources and only 1 of the
framework.s.
Big is just fine: compiles without complaint and runs as expected.
Little's framework however gets deployed to the "Resources'
directory on build.
Little will compile without any complaints but crash immediately on
'dyld: Library not loaded: @loader_path/.... Reason: image not
found'.
I've been over the compiler settings until I'm nearly bonkers but I
just don't see it....
Can somebody please give me the conceptual whack I need...
You have two targets.
Expanding each target you have a series of operations. One of these
will be "Copy Files". Its contents will be the framework(s).
Do a Get Info on the "Copy Files" item (not its contents) and choose
'Frameworks' in the destination pop-up.
hth!
--Graham
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden