> On Sep 10, 2014, at 4:50 PM, Simon Slavin <slav...@bigfraud.org> wrote: > > Don't worry too much about this. In the last count of an OS X version I > counted seven different copies of SQLite being used in various places, > integrated into programs, or as libraries, or as the shell tool. And these > are not all the same version as one-another. Apple considers each one of > these separately and doesn't have to test every single use when only one is > replaced. So if you've been clear about which copy "the built-in SQLite > library" is they can replace that one without having to retest everything > else that uses SQLite.
I'm sure there are multiple copies of SQLite inside OS X since there are a lot of low-level open source components not written by Apple, which probably link in their own copies. But the version in /usr/lib/libsqlite3.dylib is the one all Apple's software uses, and the one nearly all 3rd party apps use (because it's easier to, and they probably don't want to take the hit in code size for linking in their own copy), and the one used by Apple's Core Data framework. I can say this with some degree of authority because I worked at Apple for 15 years, six of those in the OS X group, although I left in 2007 so I'm not up to date with the way everything's currently built. But back then, if I'd built a custom copy of SQLite into my project, the integration team would have asked me some tough questions about why I wasn't using the shared system library. (BTW, I just confirmed that the final iOS 8 release is still using 3.7.13, so it's safe.) —Jens _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
