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

OS X Shared Libraries


  • Subject: OS X Shared Libraries
  • From: email@hidden
  • Date: Mon, 14 Jan 2008 10:00:31 +0000

Hi,

I'm fairly new to OS X and I have a basic question regarding shared library handling. I notice that when I run otool -L on a binary that the full path of any shared libraries is returned. Is the full path directly encoded into the executable? Does OS X have a system similar to Linux where the runtime linker searches several system paths for the required libraries? If i compile an application that generates its own libraries and then links it's executable against these libraries the hard coded path will point to the build directory. Obviously this would cause a problem when the binaries and shared libraries are installed into the system path, how is this typically avoided?

Best Regards, Simon.

_______________________________________________
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


  • Follow-Ups:
    • Re: OS X Shared Libraries
      • From: Sebastian Hagedorn <email@hidden>
  • Prev by Date: Re: Re: Launchd script question
  • Next by Date: Re: OS X Shared Libraries
  • Previous by thread: Re: Re: Launchd script question
  • Next by thread: Re: OS X Shared Libraries
  • Index(es):
    • Date
    • Thread