Re: Bundling Framework Problem
Re: Bundling Framework Problem
- Subject: Re: Bundling Framework Problem
- From: Oliver Cameron <email@hidden>
- Date: Thu, 23 Dec 2004 22:51:55 +0000
Hi,
On 23 Dec 2004, at 22:47, John C. Randolph wrote:
On Dec 23, 2004, at 2:34 PM, Oliver Cameron wrote:
Hi guys, not sure if this is supposed to go here. But its semi-cocoa
related I guess, also I'm in a real rush, I only realised this once I
released the dmg to the masses (I was doing a little app update).
Basically, users can't launch my app on their machine, but I can on
mine. A Console message revealed the problem:
dyld: /Users/Other
User/Documents/Downloads/Tag.app/Contents/MacOS/Tag can't open
library:
/Users/Me/Projects/Builds/OmniAppKit.framework/Versions/2004A/
OmniAppKit (No such file or directory, errno = 2)
I remember having this problem before, but can't remember how I fixed
it. Basically, this is what I did to add the frameworks to my app:
Dragged over frameworks to "Other Frameworks" group in Xcode.
Created a build phase and dragged the frameworks in, set it to
Frameworks/Libraries.
I've tried all sorts of various path types for it, but it just won't
work.
Any ideas at all appreciated, and again, sorry if I'm posting in the
wrong group.
You can probably get a faster answer to this kind of question in
Xcode-users in the future, but in the meantime...
I'll do that in the future for sure,
First, make sure that the path is "build product relative", and then
make sure that it's included in the app target.
Checked this, and all are "relative to build product" and I can see the
framework underneath the Frameworks & Libraries group inside the
Target.
Anymore ideas?
Thanks,
Oliver
-jcr
John C. Randolph <email@hidden> (408) 974-8819
Sr. Cocoa Software Engineer,
Apple Worldwide Developer Relations
http://developer.apple.com/cocoa/index.html
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden