Re: compiling postgres on windows - how to deal with unmatched file extension?

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.