• 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: dyld issues with library not in standard location
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: dyld issues with library not in standard location


  • Subject: Re: dyld issues with library not in standard location
  • From: Stefan Werner <email@hidden>
  • Date: Fri, 21 Oct 2005 08:51:15 +0200
  • Organization: http://freemail.web.de/


"Peter O'Gorman" <email@hidden> schrieb am 21.10.05 04:59:02:

> I'm afraid that you chose a bad example, because /usr/lib is in the default
> DYLD_FALLBACK_LIBRARY_PATH this would be found and your program would run.

In that case, skip example, repeat question: What are the benefits of having the library path encoded in the dylib file? My Xcode projects have this additional build phase with install_name_tool that they would not have in other environments. I'm sure there must be a reason why the designers of MachO included it, but from my past experience on other platforms I can't come up with any idea. What is the secret?

-Stefan


 _______________________________________________
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

  • Follow-Ups:
    • Re: dyld issues with library not in standard location
      • From: "Peter O'Gorman" <email@hidden>
  • Prev by Date: Re: STL behaving improperly
  • Next by Date: Re: I can't build with Xcode 2.2_preview3_8m639_018213953
  • Previous by thread: Re: dyld issues with library not in standard location
  • Next by thread: Re: dyld issues with library not in standard location
  • Index(es):
    • Date
    • Thread