Re: wrong Visual Studio Edition 's name

Takuma Hoshiai <[email protected]>
Newsgroups gmane.comp.db.postgresql.devel.documentation
Message-ID <[email protected]>
On Tue, 20 Aug 2019 19:19:01 +0900
Michael Paquier <[email protected]> wrote:

> On Tue, Aug 20, 2019 at 03:38:28PM +0900, Takuma Hoshiai wrote:
> > I have attached a patch. The word of "Express" existed in four
> > places, they will are fixed by this patch. 
> 
> -  These compilers can be either from <productname>Visual Studio</productname>,
> -  <productname>Visual Studio Express</productname> or some versions of the
> -  <productname>Microsoft Windows SDK</productname>. If you do not already have a
> -  <productname>Visual Studio</productname> environment set up, the easiest
> -  ways are to use the compilers from <productname>Visual Studio Express 2019
> -  for Windows Desktop</productname> or those in the <productname>Windows SDK
> +  These compilers can be either from <productname>Visual Studio</productname>
> +  or some versions of the <productname>Microsoft Windows SDK</productname>.
> +  If you do not already have a <productname>Visual Studio</productname> 
> +  environment set up, the easiest ways are to use the compilers
> +  from <productname>Visual Studio 2019</productname>
> +  or those in the <productname>Windows SDK
>    10</productname>, which are both free downloads from Microsoft.
> 
> I may be missing something, but this refers to all the possible
> flavors of VS where compilers are available, hence mentioning Visual
> Studio Express is still correct when going through our full supported
> range from VS 2013 to VS 2019, no?  That's why I said only two places
> need to be fixed, as this area is fine.

Yes, Express edition is contained by supported range. But my understanding
is that other Edition are also same. The reason for changing above sentence,
was that I thought that we don't need to specify Express edition only.

The above original sentence is no problem too, so I have reattached a patch,
which is fixed "Express 2019" only.

> --
> Michael


-- 
Takuma Hoshiai <[email protected]>
vs_edition_fix_v2.patch (application/octet-stream, 1.5 KB)
diff --git a/doc/src/sgml/install-windows.sgml b/doc/src/sgml/install-windows.sgml
index 0bbb314..c6e4afe 100644
--- a/doc/src/sgml/install-windows.sgml
+++ b/doc/src/sgml/install-windows.sgml
@@ -19,9 +19,8 @@
  <para>
   There are several different ways of building PostgreSQL on
   <productname>Windows</productname>. The simplest way to build with
-  Microsoft tools is to install <productname>Visual Studio Express 2019
-  for Windows Desktop</productname> and use the included
-  compiler. It is also possible to build with the full
+  Microsoft tools is to install <productname>Visual Studio 2019</productname>
+  and use the included compiler. It is also possible to build with the full
   <productname>Microsoft Visual C++ 2013 to 2019</productname>.
   In some cases that requires the installation of the
   <productname>Windows SDK</productname> in addition to the compiler.
@@ -69,8 +68,8 @@
   <productname>Visual Studio Express</productname> or some versions of the
   <productname>Microsoft Windows SDK</productname>. If you do not already have a
   <productname>Visual Studio</productname> environment set up, the easiest
-  ways are to use the compilers from <productname>Visual Studio Express 2019
-  for Windows Desktop</productname> or those in the <productname>Windows SDK
+  ways are to use the compilers from <productname>Visual Studio 2019</productname>
+  or those in the <productname>Windows SDK
   10</productname>, which are both free downloads from Microsoft.
  </para>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.