> -----Original Message-----
> From: mlw [mailto:markw@mohawksoft.com]
> Sent: Thursday, May 09, 2002 2:56 PM
> To: Dann Corbit
> Cc: PostgreSQL-development
> Subject: Re: Issues tangential to win32 support
>
>
> Dann Corbit wrote:
> > Our package avoids Cygwin altogether. We wrote our own
> POSIX layer from
> > scratch, and we junked fork() for CreateProcess() {and
> inserted copious:
> > #ifdef ICKY_WIN32_KLUDGE
> > /* our code goes here */
> > #else
> > /* Standard UNIX code goes here */
> > #endif
>
> OK, what sorts of things did you do in your
> ICKY_WIN32_KLUDGE? Were they ever
> migrated back into the main tree? Did you simulate fork() or
> a stand-alone?
>
> I know Windows very well, but I have thus far remained
> ignorant of PostgreSQL
> internals.
>
> >
> > It's complete, and it performs like the burning blue
> blazes. We have
> > run the full PostgreSQL test suite to completion with
> success. However,
> > before we release any SQL tool, we have our own test suite
> with tens of
> > thousands of tests to perform. Hence, we won't have a release until
> > June at the earliest.
> >
> > I think the Japanese one also does not use Cygwin (but I
> have not tried
> > installing it yet).
>
> The japanese site claims cygwin.
This is not correct. (Fortunately, we have someone here who reads and
writes Japanese).
At any rate, it is a complete, native implementation of PostgreSQL
without any need for Cygwin.
Just to be sure, I did a "depends" on each of the binaries and none of
them use Cywin.
So the Japanese site did exactly the same thing that we did.
Here are bitmaps showing the complete dependency trees of both the
Japanese efforts and ours as well:
Us:
ftp://cap.connx.com/pub/chess-engines/new-approach/connx.bmp
Japanese:
ftp://cap.connx.com/pub/chess-engines/new-approach/japanese.bmp
No Cygwin in sight in either case.
