1919 <para>
2020 There are several different ways of building PostgreSQL on
2121 <productname>Windows</productname>. The simplest way to build with
22- Microsoft tools is to install <productname>Visual Studio Express 2013
22+ Microsoft tools is to install <productname>Visual Studio Express 2015
2323 for Windows Desktop</productname> and use the included
2424 compiler. It is also possible to build with the full
25- <productname>Microsoft Visual C++ 2005 to 2013 </productname>.
25+ <productname>Microsoft Visual C++ 2005 to 2015 </productname>.
2626 In some cases that requires the installation of the
2727 <productname>Windows SDK</productname> in addition to the compiler.
2828 </para>
7777 <productname>Visual Studio Express</productname> or some versions of the
7878 <productname>Microsoft Windows SDK</productname>. If you do not already have a
7979 <productname>Visual Studio</productname> environment set up, the easiest
80- ways are to use the compilers from <productname>Visual Studio Express 2013
80+ ways are to use the compilers from <productname>Visual Studio Express 2015
8181 for Windows Desktop</productname> or those in the <productname>Windows SDK
8282 7.1</productname>, which are both free downloads from Microsoft.
8383 </para>
8484
8585 <para>
86- PostgreSQL is known to support compilation using the compilers shipped with
86+ Both 32-bit and 64-bit builds are possible with the Microsoft Compiler suite.
87+ 32-bit PostgreSQL buils are possible with
8788 <productname>Visual Studio 2005</productname> to
88- <productname>Visual Studio 2013 </productname> (including Express editions),
89+ <productname>Visual Studio 2015 </productname> (including Express editions),
8990 as well as standalone Windows SDK releases 6.0 to 7.1.
90- 64-bit PostgreSQL builds are only supported with
91+ 64-bit PostgreSQL builds are supported with
9192 <productname>Microsoft Windows SDK</productname> version 6.0a to 7.1 or
92- <productname>Visual Studio 2008</productname> and above.
93+ <productname>Visual Studio 2008</productname> and above. Compilation
94+ is supported down to <productname>Windows XP</productname> and
95+ <productname>Windows Server 2003</> when building with
96+ <productname>Visual Studio 2005</> to
97+ <productname>Visual Studio 2013</productname>. Building with
98+ <productname>Visual Studio 2015</productname> is supported down to
99+ <productname>Windows Vista</> and <productname>Windows Server 2008</>.
93100 </para>
94101
95102 <para>
@@ -210,9 +217,7 @@ $ENV{PATH}=$ENV{PATH} . ';c:\some\where\bison\bin';
210217 Both <productname>Bison</productname> and <productname>Flex</productname>
211218 are included in the <productname>msys</productname> tool suite, available
212219 from <ulink url="http://www.mingw.org/wiki/MSYS"></> as part of the
213- <productname>MinGW</productname> compiler suite. You can also get
214- <productname>msys</productname> as part of
215- <productname>msysGit</productname> from <ulink url="http://git-scm.com/"></>.
220+ <productname>MinGW</productname> compiler suite.
216221 </para>
217222
218223 <para>
@@ -221,9 +226,7 @@ $ENV{PATH}=$ENV{PATH} . ';c:\some\where\bison\bin';
221226 PATH environment variable in <filename>buildenv.pl</filename> unless
222227 they are already in PATH. In the case of MinGW, the directory is the
223228 <filename>\msys\1.0\bin</filename> subdirectory of your MinGW
224- installation directory. For msysGit, it's the <filename>bin</filename>
225- directory in your Git install directory. Do not add the MinGW compiler
226- tools themselves to PATH.
229+ installation directory.
227230 </para>
228231
229232 <note>
0 commit comments