Horton

Re: VS2022: Support Visual Studio 2022 on Windows

Michael Paquier <michael@paquier.xyz>

View thread
From: Michael Paquier <michael@paquier.xyz>
To: Dave Page <dpage@pgadmin.org>
Cc: Hans Buschmann <buschmann@nidsa.net>, Daniel Gustafsson <daniel@yesql.se>, Andrew Dunstan <andrew@dunslane.net>, Tom Lane <tgl@sss.pgh.pa.us>, Laurenz Albe <laurenz.albe@cybertec.at>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2021-11-24T11:36:27Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add support for Visual Studio 2022 in build scripts

On Wed, Nov 24, 2021 at 10:00:19AM +0000, Dave Page wrote:
> It's extremely unlikely that we'd shift to such a new version for PG15. We
> build many components aside from PostgreSQL, and need to use the same
> toolchain for all of them (we've had very painful experiences with mix n
> match CRT versions in the past) so it's not just PG that needs to support
> VS2022 as far as we're concerned

Yes, I can understand that upgrading the base version of VS used is a
very difficult exercise.  I have been through that, on Windows for
Postgres..  As well as for the compilation of all its dependencies.

> - Perl, Python, TCL, MIT Kerberos,
> OpenSSL, libxml2, libxslt etc. are all built with the same toolchain for
> consistency.

Dave, do you include LZ4 in 14?  Just asking, as a matter of
curiosity.
--
Michael