You can take a look at what Apple has done for OS X here:
http://www.opensource.apple.com/darwinsource/10.4/SQLite-28/
Don't be mislead by the project name--it is SQLite 3. I haven't
studied it closely, but it should allow you to build exactly what
Apple shipped. The Makefile has references to locking callbacks, so
this might be relevant:
# add -DSQLITE_DEBUG=1 to enable lock tracing and other debugging
features
# you also need to set sqlite3_os_trace to 1 in SQLite3/src/os_common.h
Extra_CC_Flags += -DASSERT_VIA_CALLBACK=1 -DENABLE_LOCKING_CALLBACKS=1
HTH,
Aaron
On Oct 25, 2005, at 12:45 PM, Steve Palmer wrote:
What are those reasons and is there any expectation that they can be
made available as patches for folks who build SQLite privately? I
cannot use the libsqlite3.dylib that comes with Mac OSX 10.4 since my
application needs to run on 10.3.9 too and there is no equivalent
static version that I can find.
- Steve
On Oct 25, 2005, at 4:57am, [EMAIL PROTECTED] wrote:
Steve Palmer <[EMAIL PROTECTED]> wrote:
I'm currently investigating a problem with my application, SQLite
3.2.5 and a database located on a Mac OSX Server network share that
does not seem to repro with the SQLite 3.1.3 that ships with Mac OSX
4.1. Specifically if I place a SQLite database file on a folder on a
remote network share and attempt to access it using the sqlite3
utility, I get different results.
Apple added special hacks to their release of SQLite 3.1.3 that
allow it to work on remote filesystems with broken file locking.
For various reasons, those hacks have not been incorporated into
the SQLite core, yet.
--
D. Richard Hipp <[EMAIL PROTECTED]>
