Re: Building with Visual C++

Lists: pgsql-patches
From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Chuck McDevitt" <cmcdevitt(at)greenplum(dot)com>, <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Building with Visual C++
Date: 2006-04-24 20:25:48
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCEA0F937@algol.sollentuna.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-patches

> I've done a similar thing myself (building the complete
> backend with Visual Studio 2005). I got it to basically
> work, but stopped due to lack of interest in the PostgreSQL community.

Well, I'm one of those previously with lack of interest :-)

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.

> But, I'd be happy to help out your effort in any way I can.

Thanks. There'll be plenty of pieces to pick up once I'm done with the
initial version of the script :-)

//Magnus


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
Views: Raw Message | Whole Thread | Download mbox | Resend email
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


From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-patches(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Magnus Hagander" <mha(at)sollentuna(dot)net>, "Chuck McDevitt" <cmcdevitt(at)greenplum(dot)com>
Subject: Re: Building with Visual C++
Date: 2006-05-08 20:25:53
Message-ID: 200605082225.54487.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-patches

Tom Lane wrote:
> 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?

The Coin 3D project had a wrapper program that makes VC look like a Unix
compiler. Looking at
<http://www.coin3d.org/support/coin_faq/#extension_MSVCproject> now, it
seems they have changed to autogenerating a project file as well. But
check there anyway; these guys have been doing this for years.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/