• 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: Apple library distrobution
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Apple library distrobution


  • Subject: Re: Apple library distrobution
  • From: robert delius royar <email@hidden>
  • Date: Sun, 17 Oct 2004 09:44:18 -0400 (EDT)
  • Organization: An Apple OS X end user
  • Priority: NEW

Sat, 16 Oct 2004 (20:40 -0400 UTC) David R. Morrison wrote:


On Oct 16, 2004, at 2:56 PM, robert delius royar wrote:


Is it more correct to use DYLD_FALLBACK_LIBRARY_PATH than to use DYLD_LIBRARY_PATH? DYLD_LIBRARY_PATH appears to be for testing new directories before installing them.


It's a tricky question in this particular case.

We're assuming that some users might have X11 installed, and some might not. Now, there are actually several versions of X11 which they might have installed (from Apple, from XFree86, and from X.org) and they are not all binary compatible. It might be the case that the incompatibilities won't matter for the software that the original poster was concerned with. But if they do, you want to make sure that dyld finds the *correct* copy of the library. Using DYLD_LIBRARY_PATH guarantees this, since it is searched first.

Note that the man page for dyld states that DYLD_LIBRARY_PATH is for trsting and development only. That caveat does not seem to be in the description of DYLD_FALLBACK_LIBRARY_PATH. However, on the opendarwin darwinports list there is currently a discussion about how wrong either of these variables is for a distributed system. The suggestion there is to create a bundle with @executable_path as the path to the library (including the library) or statically linking the library (I believe that meant to include an absolute path to a library in the executable, not using a static library and linking it into the executable).


Is there a way (a utility) that can change a libraries path as stored in the executable so that during installation a script could find the library on the system then change to path stored in the executable to point directly to that library?

--
 rdr
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list      (email@hidden)
This email sent to email@hidden


References: 
 >Apple library distrobution (From: Ken Mankoff <email@hidden>)
 >Re: Apple library distrobution (From: "David R. Morrison" <email@hidden>)
 >Re: Apple library distrobution (From: robert delius royar <email@hidden>)
 >Re: Apple library distrobution (From: "David R. Morrison" <email@hidden>)

  • Prev by Date: Re: Apple library distrobution
  • Next by Date: utf8 support
  • Previous by thread: Re: Apple library distrobution
  • Next by thread: Re: Apple library distrobution
  • Index(es):
    • Date
    • Thread