Nick, thanks for the tip, you set me on the right track. Here is my
new understanding of the problem. In my framework target settings, the
Dynamic Library Install Name is set to:
$(DYLIB_INSTALL_NAME_BASE:standardizepath)/$(EXECUTABLE_PATH)
This is for both Debug and Release. However these expand to different
things for debug and release:
Debug: @executable_path/../Frameworks/libxml.framework/Versions/2.7.3/
libxml
Release: /Frameworks/libxml.framework/Versions/2.7.3/libxml
Is there some good logic behind this difference? Should I just replace
$(DYLIB_INSTALL_NAMEBASE:standardizebasepath) with @executable_path/../
Frameworks? This works, but I'm curious if there is a more standard /
graceful way of doing this.
Lastly, what about @rpath? I read that this is the fancy new way to do
it in Leopard. Just replacing @executable_path with @rpath didn't
work. Do I need some other linker flag on the application side?
Thanks for all your help. I realize that perhaps these Build Settings
questions should go to the Xcode list instead.
- George
On May 6, 2009, at 5:25 PM, Nick Zitzmann wrote:
On May 6, 2009, at 6:13 PM, George King wrote:
Can anybody suggest a solution, or at least a next step for
debugging this problem?
Try searching around for information about @executable_path and
@loader_path.
Nick Zitzmann
<http://www.chronosnet.com/>
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
