Regarding the Mac OS X Framework
jordan.breeding at mac.com
Fri Oct 17 02:13:08 CEST 2008
I have seen a different problem than most here:
The framework download seems to have been built with debugs turned on
(already talked to the author and he said he would look into fixing it
the next time it is rebuilt).
Regarding the Framework linking: while the Framework could probably be
built with something more useful than /TagLib.framework/Versions/1/
TagLib you can fix it yourself one of two ways.
Way No. 1:
Use install_name_tool to change the name within the library itself --
example command (install_name_tool -id @executable_path/../Frameworks/
Way No. 2:
Use the -headerpad_max_install_names linker option while linking your
binary/framework. Then after copying the TagLib.framework bundle over
into your own binary/framework use install_name_tool to change it.
For instance (install_name_tool -change /TagLib.framework/Versions/1/
Hope that helps a little. See the man page of ld(1) and
install_name_tool(1) for more information.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3821 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/taglib-devel/attachments/20081016/acdd0b7a/attachment.p7s
More information about the taglib-devel