Re: linking shared libraries with dependent shared libraries
Re: linking shared libraries with dependent shared libraries
- Subject: Re: linking shared libraries with dependent shared libraries
- From: Paul Forgey <email@hidden>
- Date: Tue, 12 Oct 2004 20:30:44 -0700
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.
On Oct 12, 2004, at 7:58 PM, Peter O'Gorman wrote:
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.
Peter
--
Peter O'Gorman - http://www.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