• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
[SOLVED] Re: Framework Issues
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[SOLVED] Re: Framework Issues


  • Subject: [SOLVED] Re: Framework Issues
  • From: Tito Ciuro <email@hidden>
  • Date: Thu, 23 Jun 2005 19:44:20 -0400

Hi Chris,

This happened with and without ZeroLink on. Daniel Jalkut pointed me in the right direction:

Hi Tito: have you looked in the executable's Frameworks/ QuickLite.framework contents to make sure the binary is in fact there in the built product? If so, then try examining the binary with otool:

% cd /Users/tciuro/Symbols/Debug/Test.app/Contents/Frameworks/ QuickLite.frameworks/Versions/A/
% otool -L QuickLite


See if it says anything funny...

The deal with the "@executable_path" bits in the otool output means that is where the Library expects to be found by its clients. So this copy of QuickLite was built in such a way that it MUST be located inside the applications "Frameworks" folder.

For instance, if you do the same "otool -L" on a System framework, you'll see that it shows a full path as the first line of the otool output. That means that clients linking against it will expect to find it at runtime at the full path.

So, you need to decide for your project whether you want the library to go with the app or whether you want it to be installed at a known location. If you want it to go with the app (or if you just want to verify that things are working now before you decide), then you are already set up for that and just need to make sure the framework gets installed in your app's Frameworks path. You can do this from Xcode by:

0. Select the target you want to affect.
1. Project->NewBuildPhase->NewCopyFilesBuildPhase.
2. Choose "Frameworks" from the destination popup for the phase.
3. Find the QuickLite framework icon in your project's list of linked libraries, and drag it to the new build phase.


That will tell Xcode to always copy the framework into your built application's frameworks folder.

This solved the problem. Sorry for the long text. I thought it would be good to share it. Hopefully this will help someone else having a similar problem.


Thanks,

-- Tito



On 23/06/2005, at 19:35, Chris Hanson wrote:

On Jun 23, 2005, at 11:02 AM, Tito Ciuro wrote:

Could someone please tell me what does this error mean:



[Session started at 2005-06-23 13:59:48 -0400.]
dyld: Library not loaded: @executable_path/../Frameworks/ QuickLite.framework/Versions/A/QuickLite
Referenced from: /Users/tciuro/Symbols/Debug/Test.app/Contents/ MacOS/Test
Reason: image not found


Test has exited due to signal 5 (SIGTRAP).



I have added the framework as usual, but for some reason it crashes before I have a chance to debug.



Was the framework built with ZeroLink on?

-- Chris
_______________________________________________
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


References: 
 >Framework Issues (From: Tito Ciuro <email@hidden>)
 >Re: Framework Issues (From: Chris Hanson <email@hidden>)

  • Prev by Date: Re: Framework Issues
  • Next by Date: Re: Disabling "You are about to undo past the last point this file was saved" sheet?
  • Previous by thread: Re: Framework Issues
  • Next by thread: Developer Transition System - distributed builds
  • Index(es):
    • Date
    • Thread