| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, Peifeng Qiu <pqiu(at)pivotal(dot)io> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
| Subject: | Re: Compile from source using latest Microsoft Windows SDK |
| Date: | 2019-07-19 12:30:38 |
| Message-ID: | 8ad56b35-78b0-0c2a-0143-348ea63a0710@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7/19/19 5:51 AM, Michael Paquier wrote:
>
>> I'm also very curious on how hamerkop and bowerbird build postgres with
>> VS2017. Looks like hamerkop and bowerbird both exist before VS2017
>> and maybe they get SDK v8.1 from previous VS installations. I will
>> contact admin of hamerkop and bowerbird and see if that's the case.
>> As of now I can still encounter the same issue with fresh installed
>> Windows Server 2016 and VS2017, on both azure and google cloud. So
>> better to patch the build system anyway.
> I guess so but I cannot confirm myself. I am adding Andrew and Hari
> in CC to double-check if they have seen this problem or not. Hari has
> also worked on porting VS 2017 and 2019 in the MSVC scripts in the
> tree.
My tests of the VS2017 stuff used this install mechanism on a fresh
Windows instance:
choco install -y visualstudio2017-workload-vctools --package-parameters
"--includeOptional"
This installed Windows Kits 8.1 and 10, among many other things.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2019-07-19 12:41:28 | Re: Compiler warnings with MinGW |
| Previous Message | Daniel Gustafsson | 2019-07-19 12:11:02 | Re: Further hacking on SPITupleTable struct |