This is the mail archive of the
mailing list for the Cygwin project.
Re: [TEST] sqlite3-3.7.17-1 (Cygwin 1.7.19 locking feature)
- From: David Rothenberger <daveroth at acm dot org>
- To: cygwin at cygwin dot com
- Date: Wed, 05 Jun 2013 15:27:19 -0700
- Subject: Re: [TEST] sqlite3-3.7.17-1 (Cygwin 1.7.19 locking feature)
- References: <51ACF886 dot 10301 at etr-usa dot com> <51AD3BB4 dot 2010601 at acm dot org> <20130604084128 dot GB19572 at calimero dot vinschen dot de> <51AF968E dot 1060707 at etr-usa dot com>
On 6/5/2013 12:50 PM, Warren Young wrote:
> It required a spelunking expedition, complete with yak wagons and a team
> of five sherpas, one of which had to be left behind with a broken leg,
> but I figured out how to compile in the BSD locking VFS without
> disabling the POSIX one, then how to make SQLite switch between them at
> runtime. (This is what gives me hope for Plan C, above.)
Thanks again for all your effort here.
> The CYGWIN_SQLITE_LOCKING variable now has three possible states:
> CYGWIN_SQLITE_LOCKING=posix -- same as before
> CYGWIN_SQLITE_LOCKING=posixmand -- equivalent to leaving it undefined in
> the 3.7.17-1 build
> CYGWIN_SQLITE_LOCKING=AnythingElse -- BSD flock() based mandatory locking.
I think the "AnythingElse" setting is what you intended for Subversion
users that want to interoperate with Windows?
The Subversion test suite passes with that setting. I don't know about
issues with TortoiseSVN since I don't use it personally.
David Rothenberger ---- email@example.com
"Experience has proved that some people indeed know everything."
-- Russell Baker
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple