Re: automating pg_config.h.win32 maintenance

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: automating pg_config.h.win32 maintenance
Date: 2019-12-19 07:31:05
Message-ID: 78e64ab4-ff4a-0613-660c-d6429ad8d621@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-12-19 04:59, Michael Paquier wrote:
> On Tue, Dec 17, 2019 at 11:56:17AM +0100, Peter Eisentraut wrote:
>> Yeah, good idea. Attached patch is refactored so all three header files
>> managed by AC_CONFIG_HEADERS are processed the same way.
>
> Looks good. I just have one comment.
>
> + # XXX
> + open(my $f, '>>', 'src/include/pg_config.h')
> + || confess "Could not write to src/include/pg_config.h\n";
> + print $f "\n";
> + print $f "#define VAL_CONFIGURE \""
> + . $self->GetFakeConfigure() . "\"\n";
> + close($f);
>
> This part needs a comment. Like it is the equivalent of what
> src/common/'s Makefile does or something like that?

This was meant to be addressed by
<https://www.postgresql.org/message-id/flat/6e457870-cef5-5f1d-b57c-fc89cfb8a788%402ndquadrant.com>,
but that discussion has not concluded yet. Perhaps it makes more sense
in this context.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-12-19 07:49:44 Re: automating pg_config.h.win32 maintenance
Previous Message Michael Paquier 2019-12-19 07:13:08 Re: non-exclusive backup cleanup is mildly broken