• 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
Modifying dyld behavior for framework
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Modifying dyld behavior for framework


  • Subject: Modifying dyld behavior for framework
  • From: Stephan Burlot <email@hidden>
  • Date: Mon, 09 Dec 2002 23:57:15 +0100

Hi,

I'm trying to link my app with a Framework and include this framework in my
app. (I dont have access to the source of this framework)

If I start my app and the Framework is NOT in the /Library/Frameworks
folder, my app crashes miserably with a dyld error.

otool -L gives a static path for the Framework, although the Framework is
copied in the app bundle.

Question 1: can I change the behavior of a framework, even if it has not
been compiled with the @executable_path=../Frameworks?
I've tried to change DYLD_FRAMEWORK_PATH and launch with the terminal with
no success.

Question 2: how can I detect at runtime if the framework is in
/Library/Frameworks or (~/Library/Frameworks) and display a meaningful
message before dying?

Any hints or doc pointers would be great!

Thanks,
Stephan
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Modifying dyld behavior for framework
      • From: Stephan Burlot <email@hidden>
  • Prev by Date: Re: What can be thrown away in a project?
  • Next by Date: Re: Modifying dyld behavior for framework
  • Previous by thread: Re: Responder Chain and newDocument:, runPageLayout:, etc
  • Next by thread: Re: Modifying dyld behavior for framework
  • Index(es):
    • Date
    • Thread