Re: How Do I Statically Link to libcurl?
Re: How Do I Statically Link to libcurl?
- Subject: Re: How Do I Statically Link to libcurl?
- From: Michael Ash <email@hidden>
- Date: Wed, 1 Jul 2009 10:41:22 -0400
On Tue, Jun 30, 2009 at 11:49 PM, Chris Tracewell<email@hidden> wrote:
>
> On Jun 30, 2009, at 6:43 PM, Kyle Sluder wrote:
>
>> dylib means "dynamic library"...
>>
>> Why do you need to link against libcurl statically? Not saying there
>> aren't valid use cases, but please present yours.
>
> I guess I assumed that static linking is prefered as it would include
> libcurl with the executable and thus ensure that the app would work
> consistently, even if someone had a different version or had deleted this
> library from their machine. In short it just seemed like a safe option, but
> I am un-educated in this regard, so it was my best guess. The deployment
> environment is fairly easy right now, about 10 machines, mostly 10.5 with
> Intel iMac and Powerbooks which I can tweak if needed, but in the future
> this may grow and so you get the picture.
Your Cocoa application depends, directly or indirectly, on at least
half a dozen dynamic libraries to be present on the system. First off,
every binary depends on libSystem.dylib to be there. Then you need
AppKit.framework and Foundation.framework, and frameworks are just
dylibs wrapped in a pretty shell. You're also depending on Carbon,
CoreServices, Quartz, CoreFoundation, etc. If any one of these were to
be deleted, your application would no longer work.
The libcurl library ships with the system just like all these others.
It is part of the installation. You can, and should, count on it to be
there. There is no more reason to try to statically link libcurl into
your application than there is to statically link Cocoa.
Mike
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden