Windows perl/tcl requirement documentation - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Windows perl/tcl requirement documentation
Date
Msg-id 4acddcd4-1c08-44e7-ba60-cab1022599e3@dunslane.net
Whole thread Raw
Responses Re: Windows perl/tcl requirement documentation
List pgsql-hackers


Our docs currently state this regarding the perl requirement for building on Windows:


ActiveState Perl

ActiveState Perl is required to run the build generation scripts. MinGW or Cygwin Perl will not work. It must also be present in the PATH. Binaries can be downloaded from https://www.activestate.com (Note: version 5.14 or later is required, the free Standard Distribution is sufficient).


This really hasn't been a true requirement for quite some time. I stopped using AS perl quite a few years ago due to possible licensing issues, and have been building with MSVC using Strawberry Perl ever since. Andres recently complained that Strawberry was somewhat out of date, but that's no longer really the case - it's on 5.38.2, which is the latest in that series, and perl 5.40.0 was only releases a few weeks ago.

We recommend AS Tcl/Tk, which I have not used, but which I am wary of for the same reasons. There is a BSD licensed up to date windows binary installation called Magicsplat which I haven't tried but which might well be suitable for our purposes.

I suggest we remove these references to AS and replace them with references to Windows distros that are more appropriate.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: add --no-sync to pg_upgrade's calls to pg_dump and pg_dumpall
Next
From: Laurenz Albe
Date:
Subject: Re: Wrong security context for deferred triggers?