Sorry, I should have stated that I am not defining SQLITE_MUTEX_NOOP
explicitly. SQLITE_MUTEX_NOOP is defined implicitly if you let
SQLITE_THREADSAFE default to 1 and define SQLITE_OS_OTHER=1 (i.e. do not
use SQLITE_OS_UNIX, SQLITE_OS_WIN or SQLITE_OS_OS2). I know this won't
affect many people, but it's an issue if you're building for an embedded
platform.

Cheers,
Dave.


-----Original Message-----
From: D. Richard Hipp [mailto:[EMAIL PROTECTED] 
Sent: 15 October 2008 10:52
To: General Discussion of SQLite Database
Subject: Re: [sqlite] SQLite version 3.6.4


On Oct 15, 2008, at 1:31 PM, Dave Toll wrote:

> I found a small compile error when SQLITE_MUTEX_NOOP is defined with  
> the
> amalgamation source:
>

SQLITE_MUTEX_NOOP is an internal symbol that gets set if and only if  
you define SQLITE_THREADSAFE=0.  You should not set SQLITE_MUTEX_NOOP  
yourself.  Instead set SQLITE_THREADSAFE=0 and let SQLITE_MUTEX_NOOP  
be set automatically.

D. Richard Hipp
[EMAIL PROTECTED]




_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to