Re: VS2022: Support Visual Studio 2022 on Windows
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Hans Buschmann <buschmann@nidsa.net>
Cc: Andrew Dunstan <andrew@dunslane.net>,
Tom Lane <tgl@sss.pgh.pa.us>,
Michael Paquier <michael@paquier.xyz>,
Laurenz Albe <laurenz.albe@cybertec.at>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2021-11-17T14:11:24Z
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
> On 6 Nov 2021, at 10:29, Hans Buschmann <buschmann@nidsa.net> wrote: > 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. This patch fails to apply as it's anchored beneath the root of the source tree, please create the patch from inside the sourcetree such that others (and the CF patch tester) can apply it without tweaking: --- a/postgresql-14.0_orig/doc/src/sgml/install-windows.sgml +++ b/postgresql-14.0_vs2022/doc/src/sgml/install-windows.sgml Also note that patches should be against Git HEAD unless fixing a bug only present in a backbranch. > I will reflect any updates after official release on monday, November 8 Any updates on this following the November 8 release? -- Daniel Gustafsson https://vmware.com/