Re: [COMMITTERS] pgsql: Sigh ... - Mailing list pgsql-patches

From Peter Eisentraut
Subject Re: [COMMITTERS] pgsql: Sigh ...
Date
Msg-id 200805031115.03000.peter_e@gmx.net
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Sigh ...  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: [COMMITTERS] pgsql: Sigh ...  (Andrew Dunstan <andrew@dunslane.net>)
List 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.

pgsql-patches by date:

Previous
From: "Pavel Stehule"
Date:
Subject: Re: plpgsql CASE statement - last version
Next
From: Peter Eisentraut
Date:
Subject: Re: Exposing keywords to clients