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.
If you really need to, you can download the source and compile it into a library yourself. --Kyle Sluder
Well, honestly don't know a lot about libcurl and was not aware that I would need to download and compile to be able to statically link, I thought it was like curl and just already on the machine. I have already way over shot my time on this so dynamically linking is fine for now. I was going to use NSTask and curl but saw libcurl and thought it would be more efficient, but I am about to give up on it and go back to curl as I have wasted a half a day trying to "link to it."
Finally, just to be sure to be sure to steer things back to my original question... whether I dynamically link or statically link, is there a manual anywhere that describes how to do this in XCode?
Thanks Chris _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
