Re: Win32 port patches submitted

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Justin Clift <justin(at)postgresql(dot)org>, Hannu Krosing <hannu(at)tm(dot)ee>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Postgres development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Win32 port patches submitted
Date: 2003-01-29 19:47:01
Message-ID: 3E382FB5.DB0CE879@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut wrote:
>
> Justin Clift writes:
>
> > The advantages to having the Win32 port be natively compatible with
> > Visual Studio is that it already is (no toolset-porting work needed
> > there),
>
> You're missing a couple of points here. First, the MS Visual whatever
> compiler can also be used with a makefile-driven build system. Second,
> the port as it stands isn't really compatible with anything except Jan's
> build instructions. There's a lot of work to be done before we get
> anything that builds out of the box in the 7.4 branch, and it's going to
> be a lot easier if we do it using the build system we already have and
> know.

Absolutely right, I know that the build environment is more a mess than
an environment. All I said is that we have a stable, working, native
Win32 PostgreSQL 7.2.1 ...

And I don't care if we use MingW, Borland, Cygwin or a big blend of it
all, as long as the final result can be shipped binary under the BSD
license.

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dann Corbit 2003-01-29 20:00:29 Re: Win32 port patches submitted
Previous Message Tom Lane 2003-01-29 19:16:51 Re: Fix for log_min_error_messages