From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tristan Partin <tristan(at)neon(dot)tech>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: On non-Windows, hard depend on uselocale(3) |
Date: | 2024-11-25 00:42:49 |
Message-ID: | Z0PICeukFeEutR83@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Nov 23, 2024 at 10:32:31AM +1300, Thomas Munro wrote:
> I realised that there is another aspect to this: it must be impossible
> to build PostgreSQL with the original MinGW/MSYS project by now. I
> don't understand the history of the MinGW/MinGW-w64 fork, but if
> they're both still live projects out there adding to the general
> confusion about the frankenwindows multiverse, we should clarify our
> situation. As far as I know, we're only testing the second thing, and
> only the second thing can use UCRT, and only the second thing is a
> viable alternative toolchain for software that is primarily targeting
> current Visual Studio, which I think is something we can say about our
> project. Right?
FWIW, I am not seeing any advantage in mentioning MinGW at all at this
stage, just extra maintenance burden. As far as I know, MinGW is a
gcc port that has only a 32b implementation. MinGW-w64 is built on
top of it and it includes *both* 32b and 64b implementations, as you
say, with more WIN32 APIs than the former.
So +1 to simplify a bit that stuff.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2024-11-25 00:57:41 | Re: On non-Windows, hard depend on uselocale(3) |
Previous Message | Tatsuo Ishii | 2024-11-24 23:31:55 | Re: Fix for Extra Parenthesis in pgbench progress message |