On Fri, Mar 28, 2014, at 01:11 PM, Chris Hanson wrote: > You should use the SQLite that is part of the OS, and not build a > separate version. > > The same goes for all the various projects that are part of an operating > system: The versions included with a particular operating system can be > tuned for that operating system and the hardware it runs on. That doesn’t > mean they will be, but it’s something that can be done, and you should > consider that possibility when deciding whether to include your own > version of a library.
Apple has frequently advised people _not_ to link directly against system libraries included on the OS, such as libssl and libxml2, as these are included with the operating system in support of other technologies such as Security.framework and NSXMLDocument. These libraries in particular have no guarantees of API compatibility between releases, and Apple has no public or consistent policy about updating the versions included with the OS, or even about their continued inclusion. Unless and until Apple publicly announces their commitment to include a particular third-party library, and either that library has a policy of maintaining API and/or binary compatibility *or* Apple commits to maintaining such compatibility, it will always be tempting (some might say advisable) to build and include one's own version of a third-party dependency. --Kyle Sluder _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
