Skip site navigation (1) Skip section navigation (2)

Re: Building with Visual C++

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Magnus Hagander" <mha(at)sollentuna(dot)net>
Cc: "Chuck McDevitt" <cmcdevitt(at)greenplum(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Building with Visual C++
Date: 2006-04-24 20:56:39
Message-ID: 6295.1145912199@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
"Magnus Hagander" <mha(at)sollentuna(dot)net> writes:
> The main difference between what I'm trying now from most of what I've
> seen before is that I *don't* want to create a separate build
> environment that needs to be maintained. Instead have a conversion
> script from our current one to a VC compatible one.

This is definitely the only way that the project will fly --- there's
no way we're going to duplicate our forest of Makefiles in a different
format that has to be hand-maintained.  If Magnus can make a conversion
script work, though, I think we can accept that.

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.

BTW, has anyone looked at the possibility of driving VC from gmake,
so that we can continue to use the same Makefiles?  Or is that just
out of the question?

			regards, tom lane

In response to

Responses

pgsql-patches by date

Next:From: Magnus HaganderDate: 2006-04-24 21:09:18
Subject: Re: Building with Visual C++
Previous:From: Magnus HaganderDate: 2006-04-24 20:25:48
Subject: Re: Building with Visual C++

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group