Re: Clean up some old cruft related to Windows - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Clean up some old cruft related to Windows
Date
Msg-id 20200220032326.GH2288@paquier.xyz
Whole thread Raw
In response to Re: Clean up some old cruft related to Windows  (Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>)
Responses Re: Clean up some old cruft related to Windows
List 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

Attachment

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Constraint's NO INHERIT option is ignored in CREATE TABLE LIKE statement
Next
From: Andres Freund
Date:
Subject: Re: Print physical file path when checksum check fails