Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows

From: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: gaolin01(at)beyondsoft(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
Subject: Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows
Date: 2019-07-04 08:18:44
Message-ID: CAC+AXB1FbHdKwh+3JAmCOyRqecnRWCo3Tz1GzQLK07FT74OO3g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jul 3, 2019 at 1:36 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> Looking at the code, it looks to be an effect of the version checking
> in CreateProject()/MSBuildProject.pm, causing a VC2019Project object
> to be generated instead of a VC2017Project one. Your scripts seem to
> be rather advanced, and I have little idea how your installation looks
> like. What's the return result of DetermineVisualStudioVersion()?
> With VS 2017, the result is assumed to be between 14.10 and 14.20 as
> far as I know. You can also know that by looking at the version of
> nmake shipped with your installation using the native tool terminal
> for example. I guess that in your case the version of nmake is
> between 14.20.XX.YY and 15.00.NN.PP?

In that building environment, if you edit
".\src\tools\msvc\buildenv.pl" to add the following line:

$ENV{MSBFLAGS}="/p:PlatformToolset=v141";

Does it work as workaround for you?

Anyhow, could you please share what nmake version are you using?

Regards,

Juan José Santamaría Flecha

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2019-07-04 08:32:14 Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows
Previous Message Michael Paquier 2019-07-04 07:46:09 Re: BUG #15893: pg_dump is not working like as postgres version 10