Re: Clean up some old cruft related to Windows
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-02-20T03:23:26Z
Lists: pgsql-hackers
On Wed, Feb 19, 2020 at 07:02:55PM +0100, Juan José Santamaría Flecha wrote: > Please find a patched for so. I have tried to make it more version > neutral. + You can change certain build options, such as the targeted CPU + architecture, build type, and the selection of the SDK by using either + <command>VSVARS32.bat</command> or <command>VsDevCmd.bat</command> depending + on your <productname>Visual Studio</productname> release. All commands + should be run from the <filename>src\tools\msvc</filename> directory. Both commands have different ways of doing things, and don't really shine with their documentation, so it could save time to the reader to add more explicit details of how to switch to the 32-bit mode, like with "VsDevCmd -arch=x86". And I am not actually sure which environment variable to touch when using VSVARS32.bat or VSVARSALL.bat with MSVC <= 2017. -- Michael
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