site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Hi, Best Regards, Simon. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... 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? This email sent to site_archiver@lists.apple.com
participants (1)
-
elabsjng@mac.com