• 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: OS X Shared Libraries
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OS X Shared Libraries


  • Subject: Re: OS X Shared Libraries
  • From: Peter O'Gorman <email@hidden>
  • Date: Mon, 14 Jan 2008 08:58:49 -0600

Simon J. Bale wrote:
> Can I confirm that I'm correct in assuming that the library paths are
> usually hard coded into Mach-O binaries?

Library paths are usually absolute paths on Mac OS X (is this what you
mean by 'hard coded'?). It is the equivalent of using an absolute soname
on an ELF system. These install names are encoded into the libraries and
their clients in the mach-o header.

See the Xcode documentation and the manpages for ld(1), dyld(1)
install_name_tool(1) etc for more information on:

@executable_path
@loader_path
@rpath

Peter
--
Peter O'Gorman
http://pogma.com
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >OS X Shared Libraries (From: email@hidden)
 >Re: OS X Shared Libraries (From: Sebastian Hagedorn <email@hidden>)
 >Re: OS X Shared Libraries (From: "Simon J. Bale" <email@hidden>)

  • Prev by Date: Re: OS X Shared Libraries
  • Next by Date: compiling dtrace-48
  • Previous by thread: Re: OS X Shared Libraries
  • Next by thread: compiling dtrace-48
  • Index(es):
    • Date
    • Thread