Question

Update

I’ve since spent time learning how to use install_name_tool & otool to do this properly, and documented the process here: Using Frameworks Within NSBundles

---

I would like to use the Connection Kit framework within an NSBundle I am making.

To allow my bundle to load the framework successfully, I’ve changed the dynamic library install name to use @loader_path as opposed to @executable_path.

After building and including the framework in my NSBundle, then building that, running the program that loads my bundle, my bundle fails to load and produces the following output:

Error loading MyBundle.rwplugin/Contents/MacOS/MyBundle:  dlopen(/Users/facelap/Library/Developer/Xcode/DerivedData/MyBundle-hiyhdkndcnuhspfqwcuyneqobeou/Build/Products/Debug/MyBundle.rwplugin/Contents/MacOS/MyBundle, 265): Library not loaded: @executable_path/../Frameworks/DAVKit.framework/Versions/A/DAVKit
  Referenced from: /Users/facelap/Library/Developer/Xcode/DerivedData/MyBundle-hiyhdkndcnuhspfqwcuyneqobeou/Build/Products/Debug/MyBundle.rwplugin/Contents/MacOS/../Frameworks/Connection.framework/Versions/A/Connection
  Reason: image not found

It seems that Connection Kit itself uses a framework.

I also have the source for this framework. I tried setting its dynamic library install name to @loader_path, but this resulted in similar output (and the bundle failed to loar).

What would a sane entry be for the dynamic library install name for a framework within a framework that is to be used within an NSBundle?

Answer 1

Look at the crash log. It says that you bundle can’t load DAVKit.framework so the easiest way – its rebuild ConnectionKit framework but instead of embedding DAVKit.xcodeproj insert all sources of DAVKit. Its easiest way but more correctly – its setup install path of ConnectionKit and DAVKit frameworks.
Its link should help you:
embedding frameworks in loadable bundles