Re: Have dylib, want to preserve drag-install
Re: Have dylib, want to preserve drag-install
- Subject: Re: Have dylib, want to preserve drag-install
- From: Peter Mulholland <email@hidden>
- Date: Sat, 13 Oct 2007 16:42:30 +0100
Hello Scott,
Saturday, October 13, 2007, 4:01:51 PM, you wrote:
> OK, my app is completely self-contained. Drag to install, drag again to
> update, drag to trash to uninstall, no extra stuff (except prefs) left
> behind.
> Now I want to add functionality provided by a 3rd-party library, and that
> library is only provided as a set of 6 dylibs whose installer puts them into
> /Library/FooLib/lib. I don't *want* to have an installer, and I'd prefer not
> to deal with weak linking.
> Is there any way to:
> - convert a dylib to a static library;
No
> - or set up the build so that the app loads these dylibs from
> Resources/FooLib relative to the current bundle, (or ../Resources/FooLib
> relative to the current executable);
Yes - look at install_name_tool. You can change it so that the dylibs
expect to be in "@executable_path" which would then let you put them
in your bundle, in Contents/MacOS/
> - or set up the build to statically link a dynamic library.
No
--
Best regards,
Peter mailto:email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden