Re: Building with Visual C++

> -----Original Message-----
> From: pgsql-patches-owner(at)postgresql(dot)org
> [mailto:pgsql-patches-owner(at)postgresql(dot)org] On Behalf Of Dave Page
> Sent: 24 April 2006 22:35
> To: Tom Lane; Magnus Hagander
> Cc: Chuck McDevitt; pgsql-patches(at)postgresql(dot)org
> Subject: Re: [PATCHES] Building with Visual C++
>
>
>
> > -----Original Message-----
> > From: pgsql-patches-owner(at)postgresql(dot)org
> > [mailto:pgsql-patches-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
> > Sent: 24 April 2006 21:57
> > To: Magnus Hagander
> > Cc: Chuck McDevitt; pgsql-patches(at)postgresql(dot)org
> > Subject: Re: [PATCHES] Building with Visual C++
> >
> > We'll need a VC buildfarm member in place to catch us anytime we
> > change the Makefiles in a way that the script doesn't understand.
> > Before the buildfarm existed I'd have been skeptical of
> whether even
> > the conversion-script approach would be viable in the long run, but
> > with timely info about breakages I think it can work.
>
> Not a problem - Snake has VC++ 6, 2003 and 2005 installed.

Y'know I say that, but thinking about it I imagine the buildfarm is tied
well and truly into the GNU build system - running configure, make,
regression tests etc. We'd need to talk Andrew into modifying the code
to handle the different build procedure, and figure out how to run the
regression tests (prolly still need mingw for that - though possibly
SFU/Interix would work).

Regards, Dave.