Re: Prebinding problems with shared framework
Re: Prebinding problems with shared framework
- Subject: Re: Prebinding problems with shared framework
- From: Eric Albert <email@hidden>
- Date: Sat, 27 Mar 2004 15:57:35 -0800
At 10:16 PM +0100 3/24/04, Dario Accornero wrote:
On 24 Mar 2004, at 20:32, Matthew Formica wrote:
If you run from the commandline
otool -L /path/to/OpenAL.framework/Versions/A/OpenAL
/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL:
@executable_path/../Frameworks/OpenAL.framework/Versions/A/OpenAL
(compatibility version 1.0.0, current version 1.0.0)
And there's the problem. Whoever built the OpenAL framework built it
with the install name above -- the @executable_path path. When you
link against it, the linker embeds that path in your application, and
when fix_prebinding runs, it gets confused because the framework
isn't where it's supposed to be.
If you can rebuild OpenAL, rebuild it with an install name under
/Library/Frameworks, then relink your application against it and
everything will work. Alternatively, use install_name_tool to change
the install name of OpenAL to the /Library/Frameworks path.
(Normally using install_name_tool is a bit iffy because it requires
enough space when the library was built to fit the new path -- hence
the -headerpad_max_install_names option to ld -- but in this case
your new path will be shorter than the existing one so it should work
fine.)
Hope this helps,
Eric
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.