site_archiver@lists.apple.com Delivered-To: Darwin-dev@lists.apple.com On Oct 12, 2004, at 7:58 PM, Peter O'Gorman wrote: Peter -- Peter O'Gorman - http://www.pogma.com _______________________________________________ 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... Yuck, but that worked. In a lot of ways I guess this has advantages because it allows the executables to be more resistant to library path environment attacks. But still, it really complicates the build process relative to the other platforms. The dynamic linker (dyld) will not find libraries like this if they are not in one of the default search paths (/lib /usr/lib /usr/local/lib $HOME/lib). I think you need to use install_name_tool(1). I suggest that you use the -headerpad_max_install_names flag and set the install_name of the libraries to /path/to/build/loc/libname.dylib. Then the libraries can find each other at build time. At install time, you can use the install_name_tool to change the libraries names. If the libs are going to be installed relative to the executable, you should make the install_name @executable_path/rel/path/to/libname.dylib. This email sent to site_archiver@lists.apple.com