SEO

#1 (**permalink**) 04-11-2008, 05:31 AM

> -----Original Message-----
> From: Andrew Dunstan [mailto:andrew@dunslane.net]
> Sent: 01 September 2005 03:31
> To: William ZHANG
> Cc: Dave Page; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Call for 7.5 feature completion
>
>
> We currently have nmake files for the client libraries,

And even those are a royal pain to maintain, never mind an entire set.

Besides, I'm sure what William really wants is not nmake files, but VC++
Project files - but then which version do we keep? It's not like we
could say that everyone should be using VS2005, so all commits would
have to be VC++ 6.0 or earlier compatible, otherwise someone is bound to
complain.

I agree with Andrew though - maintaining VC++ project files or nmake
files is just not practical - especially given that most of our
developers are not Windows users.

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

#2 (**permalink**) 04-11-2008, 05:31 AM

----- Original Message -----
> From: "Dave Page" <dpage@vale-housing.co.uk>
> To: "Andrew Dunstan" <andrew@dunslane.net>; "William ZHANG" <uniware@zedware.org>
> Cc: <pgsql-hackers@postgresql.org>
> Sent: Thursday, September 01, 2005 3:21 PM
> Subject: RE: [HACKERS] Call for 7.5 feature completion

> > And even those are a royal pain to maintain, never mind an entire set.

> Besides, I'm sure what William really wants is not nmake files, but VC++
> Project files - but then which version do we keep? It's not like we
> could say that everyone should be using VS2005, so all commits would
> have to be VC++ 6.0 or earlier compatible, otherwise someone is bound to
> complain.

You are right. What I want is VC++ projects(*.dsp, *.dsw). Once the
project files is created, the maintance work is simply add/remove some
new/deleted source files (*.c only) from the dsps.

And I think VC++ 6.0 is ok, it is power enough and not so big for pgsql's
development. And latter versions of VC++ can automatically convert 6.0's
project files. There are also a "VC++7 to VC++6 project converter" on
www.codeproject.com.

> I agree with Andrew though - maintaining VC++ project files or nmake
> files is just not practical - especially given that most of our
> developers are not Windows users.

I am expecting more and more Windows users to join us.
According to Andrew's advice, I will try to start a project on pgfoundry
to provide the VC++ project files.

> Regards, Dave.
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

#3 (**permalink**) 04-11-2008, 05:34 AM

William ZHANG wrote:
> ----- Original Message -----
> > From: "Dave Page" <dpage@vale-housing.co.uk>
> > To: "Andrew Dunstan" <andrew@dunslane.net>; "William ZHANG" <uniware@zedware.org>
> > Cc: <pgsql-hackers@postgresql.org>
> > Sent: Thursday, September 01, 2005 3:21 PM
> > Subject: RE: [HACKERS] Call for 7.5 feature completion
>
>
> > > And even those are a royal pain to maintain, never mind an entire set.
>
> > Besides, I'm sure what William really wants is not nmake files, but VC++
> > Project files - but then which version do we keep? It's not like we
> > could say that everyone should be using VS2005, so all commits would
> > have to be VC++ 6.0 or earlier compatible, otherwise someone is bound to
> > complain.
>
> You are right. What I want is VC++ projects(*.dsp, *.dsw). Once the
> project files is created, the maintance work is simply add/remove some
> new/deleted source files (*.c only) from the dsps.
>
> And I think VC++ 6.0 is ok, it is power enough and not so big for pgsql's
> development. And latter versions of VC++ can automatically convert 6.0's
> project files. There are also a "VC++7 to VC++6 project converter" on
> www.codeproject.com.

Also, how do you build the backend with VC without the MinGW
compatibility routines and include files? I know everyone is focused on
the build environment and shell script support, but there is also
library code translation support in MinGW too that we use.

--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

#4 (**permalink**) 04-11-2008, 05:35 AM

"Bruce Momjian" <pgman@candle.pha.pa.us> wrote
>> William ZHANG wrote:
> > ----- Original Message -----
> > > From: "Dave Page" <dpage@vale-housing.co.uk>
> > > To: "Andrew Dunstan" <andrew@dunslane.net>; "William ZHANG"
<uniware@zedware.org>
> > > Cc: <pgsql-hackers@postgresql.org>
> > > Sent: Thursday, September 01, 2005 3:21 PM
> > > Subject: RE: [HACKERS] Call for 7.5 feature completion
> >
> >
> > > > And even those are a royal pain to maintain, never mind an entire
set.
> >
> > > Besides, I'm sure what William really wants is not nmake files, but
VC++
> > > Project files - but then which version do we keep? It's not like we
> > > could say that everyone should be using VS2005, so all commits would
> > > have to be VC++ 6.0 or earlier compatible, otherwise someone is bound
to
> > > complain.
> >
> > You are right. What I want is VC++ projects(*.dsp, *.dsw). Once the
> > project files is created, the maintance work is simply add/remove some
> > new/deleted source files (*.c only) from the dsps.
> >
> > And I think VC++ 6.0 is ok, it is power enough and not so big for
pgsql's
> > development. And latter versions of VC++ can automatically convert 6.0's
> > project files. There are also a "VC++7 to VC++6 project converter" on
> > www.codeproject.com.
>
> Also, how do you build the backend with VC without the MinGW
> compatibility routines and include files? I know everyone is focused on
> the build environment and shell script support, but there is also
> library code translation support in MinGW too that we use.

At first, I thought about telling Makfiles to use VC++'s command line
CL.exe, LINK.exe. But it is too difficult. Now I want to try in another
way.

1. Configure, make, make install pgsql in MinGW first.
Bison/flex and the shell scripts will generate some needed files.
2. Build with VC++.
We can use its IDE or command line MSDEV.exe.

We can now elimate most of the difficulty, and make the VC++ projects
an addon.

> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman@candle.pha.pa.us | (610) 359-1001
> + If your life is a hard drive, | 13 Roberts Road
> + Christ can be your backup. | Newtown Square, Pennsylvania
19073
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Re: Call for 7.5 feature completion