Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.) - Mailing list pgsql-hackers

From Jan Urbański
Subject Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.)
Date
Msg-id 4D2E26CA.1010806@wulczer.org
Whole thread Raw
In response to Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.)  (Jan Urbański <wulczer@wulczer.org>)
Responses Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.)  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 12/01/11 19:57, Jan Urbański wrote:
> On 11/01/11 21:21, Jan Urbański wrote:
>> On 11/01/11 18:59, Tom Lane wrote:
>>> =?UTF-8?B?SmFuIFVyYmHFhHNraQ==?= <wulczer@wulczer.org> writes:
>>>> On 11/01/11 17:11, Tom Lane wrote:
>>> Peter would probably be a better person than me to answer that, but I
>>> imagine that what you want is similar to what src/backend/Makefile does
>>> for parser/gram.h, only applied at the src/ level or maybe even the
>>> root.
>
>> And actually, if I change my rule to read:
>>
>> $(SUBDIRS:%=all-%-recurse): $(top_builddir)/src/include/utils/errcodes.h
>>
>> it works. Now whether that's acceptable or not is another thing entirely...
>
> And so I came up with three patches to make errcodes.h, plerrcodes.h and
> errcodes.sgml (respectively) generated files.

Darn, forgot about MSVC again. See
http://archives.postgresql.org/message-id/4D2DF996.9000100@wulczer.org
for details on how this works.

Attached are the previous 3 patches and a fourth one that adds MSVC support.

Cheers,
Jan

Attachment

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: arrays as pl/perl input arguments [PATCH]
Next
From: Andreas Karlsson
Date:
Subject: Re: Bug in pg_describe_object, patch v2