• 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
Re: Managing executable frameworks for multiple projects
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Managing executable frameworks for multiple projects


  • Subject: Re: Managing executable frameworks for multiple projects
  • From: Markus Hitter <email@hidden>
  • Date: Sat, 15 Nov 2003 11:01:36 +0100

Am 15.11.2003 um 10:11 schrieb Dave Rehring:

My understanding of the technical reason why ~/Library/Frameworks/ doesn't easily work is because when your application links against the framework, it includes an absolute path to the framework.

You are right. Setting the DYLD_FRAMEWORK_PATH environment variable (or some extra code, of course) should help. See "man dyld".


But as we both said, good reasons for such extra requirements are rare ...


Markus

- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: Managing executable frameworks for multiple projects (From: Dave Rehring <email@hidden>)

  • Prev by Date: Re: Managing executable frameworks for multiple projects
  • Next by Date: Why does Xcode's GDB Stop in "dyld_func_lookup_pointer"?
  • Previous by thread: Re: Managing executable frameworks for multiple projects
  • Next by thread: Re: Managing executable frameworks for multiple projects
  • Index(es):
    • Date
    • Thread