On 7/25/2013 04:29, Richard Hipp wrote:
Native, pure-blooded windows binaries run just fine on cygwin, right?
Mostly, yes.
There are exceptions. The Windows console infrastructure isn't as
general and as easy to hook into a the Unix TTY equivalent, so there are
programs that only work properly in a native Windows console. Programs
in this class typically fail when run in mintty, or under screen, or via
Cygwin ssh.
So why are we complicating the code with exceptions, special cases, and
hacks for cygwin?
Ideally, Cygwin should be treated as just another Unix-like OS.
Unfortunately, it runs on top of a Windows kernel, which simply doesn't
do some things in a way that allows it to provide proper POSIX/Linux
semantics. Over time, Cygwin has gotten better at patching over these
differences, but some are intractable enough that they remain. Part of
the problem is a need to continue working with the native Windows side
of things.
The mandatory vs advisory file locking stuff is a good example. I
assume you're aware -- at least peripherally -- of the changes that
happened to Cygwin SQLite recently. It's all an attempt to paper over
yet another of these differences between Windows and POSIX semantics.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
