Re: Clean up some old cruft related to Windows
| От | Juan José Santamaría Flecha |
|---|---|
| Тема | Re: Clean up some old cruft related to Windows |
| Дата | |
| Msg-id | CAC+AXB0J7tAqW_2F1fCE4Dh2=Ccz96TcLpsGXOCvka7VvWG9Qw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Clean up some old cruft related to Windows (Kyotaro Horiguchi <horikyota.ntt@gmail.com>) |
| Ответы |
Re: Clean up some old cruft related to Windows
Re: Clean up some old cruft related to Windows |
| Список | 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.
Using VS2019 and VS2017 this would be done using VsDevCmd.bat [2], while VS2015 and VS2013 use VSVARS32.bat.
Regards,
Juan José Santamaría Flecha
В списке pgsql-hackers по дате отправления: