Re: Bundling Framework Problem

FROM : John C. Randolph
DATE : Thu Dec 23 23:47:28 2004

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...



First, make sure that the path is "build product relative", and then 
make sure that it's included in the app target.



-jcr



John C. Randolph <<email_removed>> (408) 974-8819
Sr. Cocoa Software Engineer,
Apple Worldwide Developer Relations
http://developer.apple.com/cocoa/index.html