I use xcode 4 to build a cocoa application with a private dylib/framework.
In my development Mac, I put the dylib in the /usr/local/lib directory, and drag it into the project.
The app is compiled and runs perfect on my computer.
To distribute this app to the other Mac, I create a copy Files building phase, and say "copy that dylib to Frameworks directory".
The application is built successfully, and I indeed see the dylib is copied to the Frameworks directory in the app bundle.
The problem is when I run this app in another regular Mac, which does not have this dylib installed. I get an error saying:
dyld: Library not loaded: /usr/local/lib/mylib.dylib
Best Answer
The issue comes from the fact that you copy the framework into the app bundle, so it is available at a location like:
but you try to load it from
/usr/local/lib
where it is not available on you deployment machine. From Apple Framework Programming Guide:Now, you say that the build phase is ok; I assume also that you sent the application target build setting correctly. What is left is configuring the framework target’s installation directory.
If you did not build the framework yourself, you should be able to fix this by changing the framework install path so that it is defined relative to the loader (your app), to something like:
@loader_path/../Frameworks/
(or@executable_path/../Frameworks
). You can do that by means of install_name_tool.If you are compiling on your own the private framework, you can define its install location in Xcode build settings.