On May 6, 2009, at 18:31 , George King wrote:
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 a particular reason you are embedding a version of libxml
rather than the one that ships with the system ( /usr/lib/
libxml2.dylib )? Does the somewhat newer version have features that
you need or have needed bugfixes?
Marcel
_______________________________________________
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
