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

Re: [COMMITTERS] pgsql: Sigh ...

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-patches(at)postgresql(dot)org
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: [COMMITTERS] pgsql: Sigh ...
Date: 2008-05-03 09:15:01
Message-ID: 200805031115.03000.peter_e@gmx.net (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackerspgsql-patches
Andrew Dunstan wrote:
> This patch should fix things for both sets of changes. And it
> demonstrates pretty much what you need to do for config options for MSVC.

Btw., it is quite easily possible to use the autom4te tracing facility to 
parse the configure.ac file, in case you are interested in generating some of 
the Windows build code automatically.

For example:

$ autoconf -t 'AC_ARG_ENABLE:$1' configure.in
integer-datetimes
nls
shared
rpath
spinlocks
debug
profiling
dtrace
segmented-files
depend
cassert
thread-safety
thread-safety
thread-safety-force
largefile

Let me know if you want to do something with that.

In response to

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2008-05-03 13:11:26
Subject: Re: [COMMITTERS] pgsql: Sigh ...
Previous:From: Peter EisentrautDate: 2008-05-03 09:06:56
Subject: Re: ecpg localization

pgsql-committers by date

Next:From: Andrew DunstanDate: 2008-05-03 13:11:26
Subject: Re: [COMMITTERS] pgsql: Sigh ...
Previous:From: User H-saitoDate: 2008-05-03 07:27:37
Subject: psqlodbc - psqlodbc: Prep next release.

pgsql-patches by date

Next:From: Peter EisentrautDate: 2008-05-03 09:17:38
Subject: Re: Exposing keywords to clients
Previous:From: Pavel StehuleDate: 2008-05-03 08:12:13
Subject: Re: plpgsql CASE statement - last version

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