AW: VS2022: Support Visual Studio 2022 on Windows

Hans Buschmann <buschmann@nidsa.net>

From: Hans Buschmann <buschmann@nidsa.net>

To: Andrew Dunstan <andrew@dunslane.net>, Tom Lane <tgl@sss.pgh.pa.us>

Cc: Michael Paquier <michael@paquier.xyz>, Laurenz Albe <laurenz.albe@cybertec.at>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2021-11-06T09:29:34Z

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 →

Add support for Visual Studio 2022 in build scripts
- 82881a9b9d0f 10.20 landed
- 1061e41ff9ae 11.15 landed
- 420d5e40b3a3 12.10 landed
- baef657d3c84 13.6 landed
- 0e681fa45875 14.2 landed
- b2265d305d81 15.0 landed

Attachments

0001_support_vs2022_v2.patch (application/octet-stream) patch v2

Now it is three days before release of VS2022.

I updated to the latest Preview 7 (= RC3) and recompiled PG14 64bit Release without issues.
There seem to be not many internal differences from previous versions in the tools used for building Postgres.

My intention for an early support is to catch the momentum for signalling to any user:  "We support current tools".
The risks seem non-existent.

Updated the patch to reflect the VisualStudioVersion for Preview 7, which is the version number compiled into the main  devenv.exe image.
This version number seems to be of no interest elsewhere in the postgres source tree.

I will reflect any updates after official release on monday, November 8

Hans Buschmann