Re: Clean up MinGW def file generation

Поиск
Список
Период
Сортировка
Искать
От
Peter Eisentraut
Тема
Re: Clean up MinGW def file generation
Дата
Msg-id
90cd400d-16a7-67c9-777f-3aea58edacb0@2ndquadrant.com
Ответ на
Список
Дерево обсуждения
Clean up MinGW def file generation Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: Clean up MinGW def file generation Michael Paquier <michael@paquier.xyz>
Re: Clean up MinGW def file generation Alvaro Herrera <alvherre@2ndquadrant.com>
Re: Clean up MinGW def file generation Tom Lane <tgl@sss.pgh.pa.us>
Re: Clean up MinGW def file generation Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: Clean up MinGW def file generation Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: Clean up MinGW def file generation Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
On 2019-10-18 15:00, Tom Lane wrote:
> Yeah, the comment that Peter complained about is mine.  I believe the
> desire to avoid depending on "sed" at build time was focused on our
> old support for building libpq with Borland C (and not much else).
> Since this makefile infrastructure is now only used for MinGW, I agree
> we ought to be able to quit shipping those files in tarballs.

Yeah, it all makes sense now.  I have committed my patch now.

> I think there could be some .gitignore cleanup done along with this.
> Notably, I see exclusions for /exports.list in several places, but no
> other references to that name --- isn't that an intermediate file that
> we used to generate while creating these files?

exports.list is built from exports.txt on non-Windows platforms and
AFAICT it is not cleaned up as an intermediate file.  So I think the
current arrangement is correct.

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


В списке pgsql-hackers по дате отправления
От: Peter Eisentraut
Дата:
От: Andreas Karlsson
Дата:
FAQ