Re: MSVC Build support with visual studio 2019

From: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
To: Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: MSVC Build support with visual studio 2019
Date: 2019-05-27 10:14:02
Message-ID: CAC+AXB1qMGDg=-xP2Yjzv9=Fx8bj500SiSPBBVACuj0wr_q1hg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 23, 2019 at 3:44 AM Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
wrote:

>
> Updated patches are attached for all branches.
>
>
I have gone through all patches and there are a couple of typos:

1. s/prodcutname/productname/

1.1 In file: 0001-support-building-with-visual-studio-2019_v9.4.patch
@@ -97,8 +97,9 @@
<productname>Visual Studio 2013</productname>. Building with
<productname>Visual Studio 2015</productname> is supported down to
<productname>Windows Vista</> and <productname>Windows Server 2008</>.
- Building with <productname>Visual Studio 2017</productname> is supported
- down to <productname>Windows 7 SP1</> and <productname>Windows Server
2008 R2 SP1</>.
+ Building with <productname>Visual Studio 2017</productname> and
+ <prodcutname>Visual Studio 2019</prodcutname> are supported down to

1.2 In file:
0001-support-building-with-visual-studio-2019_v10_to_v9.5.patch
@@ -97,8 +97,9 @@
<productname>Visual Studio 2013</productname>. Building with
<productname>Visual Studio 2015</productname> is supported down to
<productname>Windows Vista</> and <productname>Windows Server 2008</>.
- Building with <productname>Visual Studio 2017</productname> is supported
- down to <productname>Windows 7 SP1</> and <productname>Windows Server
2008 R2 SP1</>.
+ Building with <productname>Visual Studio 2017</productname> and
+ <prodcutname>Visual Studio 2019</prodcutname> are supported down to

2. s/stuido/studio/

2.1 In file: 0001-support-building-with-visual-studio-2019_v9.4.patch
@@ -143,12 +173,12 @@ sub DetermineVisualStudioVersion
sub _GetVisualStudioVersion
{
my ($major, $minor) = @_;
- # visual 2017 hasn't changed the nmake version to 15, so still using the
older version for comparison.
+ # The major visual stuido that is suppored has nmake version >= 14.20 and
< 15.

2.2 In file:
0001-support-building-with-visual-studio-2019_v10_to_v9.5.patch
@@ -132,12 +162,12 @@ sub DetermineVisualStudioVersion
sub _GetVisualStudioVersion
{
my ($major, $minor) = @_;
- # visual 2017 hasn't changed the nmake version to 15, so still using the
older version for comparison.
+ # The major visual stuido that is suppored has nmake version >= 14.20 and
< 15.

2.3 In file: 0001-support-building-with-visual-studio-2019_v11.patch
@@ -139,12 +165,12 @@ sub _GetVisualStudioVersion
{
my ($major, $minor) = @_;

- # visual 2017 hasn't changed the nmake version to 15, so still using the
older version for comparison.
+ # The major visual stuido that is suppored has nmake version >= 14.20 and
< 15.

2.4 In file: 0001-Support-building-with-visual-studio-2019_HEAD.patch
@@ -106,17 +132,17 @@ sub _GetVisualStudioVersion
{
my ($major, $minor) = @_;

- # visual 2017 hasn't changed the nmake version to 15, so still using the
older version for comparison.
+ # The major visual stuido that is suppored has nmake version >= 14.20 and
< 15.

Other than that, since this is affects comments and docs, I have already
tested that the patches build and pass tests on all the intended versions.

Regards,

Juan José Santamaría Flecha

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sascha Kuhl 2019-05-27 10:40:07 Re: Indexing - comparison of tree structures
Previous Message Amit Kapila 2019-05-27 09:58:58 Re: POC: Cleaning up orphaned files using undo logs