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

Browse pgsql-committers by date

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

Browse pgsql-hackers by date

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

Browse pgsql-patches by date

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