Re: compiling postgres on windows - how to deal with unmatched file extension? - Mailing list pgsql-general

From David G. Johnston
Subject Re: compiling postgres on windows - how to deal with unmatched file extension?
Date
Msg-id CAKFQuwaDY6KF6vy_jm=KeXZsBSMGnq27Cr1vcshQJds=QdS7yQ@mail.gmail.com
Whole thread Raw
In response to compiling postgres on windows - how to deal with unmatched file extension?  ("Yang, T. Andy" <tyang99@yahoo.com>)
List pgsql-general
On Tue, Dec 13, 2022 at 9:56 PM Yang, T. Andy <tyang99@yahoo.com> wrote:
I checked out source code from the latest master version on github. I was expecting the build would go smoothly since I didn't modify anything.

That philosophy unfortunately doesn't work here.  There are many pre-requisites and there isn't a package.json equivalent kind of file in which we can define all of our dependencies (especially due to the lack of intermediary engine like the JVM or Node to cover over platform differences) so that the build is fully self-contained.  Instead we have to document those requirements in the documentation (they are indirectly documented in the configuration files/scripts I suppose...).


The msvc README in the repo also covers these two extensions explicitly:


pgbison.pl             internal tool to process .y files using bison
pgflex.pl              internal tool to process .l files using flex

David J.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: compiling postgres on windows - how to deal with unmatched file extension?
Next
From: Niels Jespersen
Date:
Subject: SV: compiling postgres on windows - how to deal with unmatched file extension?