Using install_name_tool changes functionality of library
Using install_name_tool changes functionality of library
- Subject: Using install_name_tool changes functionality of library
- From: Mike Jackson <email@hidden>
- Date: Thu, 17 May 2007 15:17:31 -0400
I have run up on a problem that I just can not figure out. Here is
what is happening. I have a 3rd party library (HDF5 v1.6.5) that I
compile just fine using the supplied autoconf based tools. The
library gets installed into /usr/local/lib.
I am now creating a GUI app that depends on that library and I
would like to include it in my application bundle in the usual way. I
set up a copy phase to copy the file to the PlugIns directory with in
the app bundle. I then run install_name_tool to change the "id" to
@executable_path/../PlugIns/libhdf5.dylib
The main part of my app links fine against this library (I can
run otool -L and see in the list of libraries the libhdf5.dylib with
the @executable_path prepended to it).
Now the fun begins. When I run my application and use a function
from the hdf5 library I will get HDF5 Errors. If I do NOT run
install_name_tool, and leave the library in /usr/local/lib and link
against it there then I will receive no errors when running the program.
This is completely reproducible on my system. Could some one shed
some light on what might be going on? What happens if the autotools
stuff did not compile the library with that "header_max_pad_install"
flag? Would install_name_tool let me know that there was a problem?
Just grasping for something..
Thanks for any/all help.
--
Mike Jackson
imikejackson & gmail * com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden