I had similar issues when wanting to load a framework. My specific problem was loading the framework in an application that was then being loaded when I was using IBDesignable.
This article by Mike Ash was extremely helpful at understanding what was happening. https://www.mikeash.com/pyblog/friday-qa-2009-11-06-linking-and-install-names.html <https://www.mikeash.com/pyblog/friday-qa-2009-11-06-linking-and-install-names.html> I think your issue is that when linking your framework you need to set the installation directory path to @rpath. You have done half of what you need by setting Runpath Search Path to loader_path/../Frameworks. Once your have changed the installation directory when building the framework you will also need to change the Runpath Search Path when linking your application. I hope that helps. Kevin > On 2 Jul 2015, at 20:12, Juanjo Conti <jjco...@carouselapps.com> wrote: > > More on this. It I change the Runpath Search Path for the target in > question to use loader_path instead of executable_path, the error still > mention executable_path. Why? > > _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
