Re: Clean up some old cruft related to Windows
Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
From: Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-02-18T11:26:06Z
Lists: pgsql-hackers
On Tue, Feb 18, 2020 at 9:56 AM Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote: > > https://www.postgresql.org/docs/current/install-windows-full.html > > In recent SDK versions you can change the targeted CPU architecture, > > build type, and target OS by using the setenv command, e.g. setenv > > /x86 /release /xp to target Windows XP or later with a 32-bit > > release build. See /? for other options to setenv. All commands > > should be run from the src\tools\msvc directory. > > AFAICS we cannot use "setenv command" on cmd.exe, or no such command > found in the msvc directory. > > I cannot point when SetEnv.bat was exactly dropped, probably Windows 7 SDK was the place where it was included [1], so that needs to be updated. Using VS2019 and VS2017 this would be done using VsDevCmd.bat [2], while VS2015 and VS2013 use VSVARS32.bat. [1] https://docs.microsoft.com/en-us/previous-versions/visualstudio/windows-sdk/ff660764(v=vs.100)?redirectedfrom=MSDN [2] https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-options/how-to-set-environment-variables-for-the-visual-studio-command-line Regards, Juan José Santamaría Flecha
Commits
-
Doc: Fix instructions to control build environment with MSVC
- 4c95ce048327 12.3 landed
- dca3911a81f0 13.0 landed
-
Clean up some code, comments and docs referring to Windows 2000 and older
- e2e02191e233 13.0 landed