Installation Path in the information of the library target isn't set.
This won't work. Dylibs (and Bundles and Frameworks) have the
installation path written into the final binary. It's an absolute path
for system wide dylibs and a path relative to the executable for
embedded Frameworks and PlugIns.
Then as I described former, when I move those files in to somewhere
else, the app doesn't run.
Because the path written into the binary doesn't fit any longer.
In fact I'd like to put the library in "MacOS" directory or any other
directory in the application bundle, ...
How to embed a Framework or plug in's into an application is well
documented. Search for "creating a private embedded framework" in
Xcode's documentation as a starter.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
