19
19
<para>
20
20
There are several different ways of building PostgreSQL on
21
21
<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
23
23
for Windows Desktop</productname> and use the included
24
24
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>.
26
26
In some cases that requires the installation of the
27
27
<productname>Windows SDK</productname> in addition to the compiler.
28
28
</para>
77
77
<productname>Visual Studio Express</productname> or some versions of the
78
78
<productname>Microsoft Windows SDK</productname>. If you do not already have a
79
79
<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
81
81
for Windows Desktop</productname> or those in the <productname>Windows SDK
82
82
7.1</productname>, which are both free downloads from Microsoft.
83
83
</para>
84
84
85
85
<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
87
88
<productname>Visual Studio 2005</productname> to
88
- <productname>Visual Studio 2013 </productname> (including Express editions),
89
+ <productname>Visual Studio 2015 </productname> (including Express editions),
89
90
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
91
92
<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</>.
93
100
</para>
94
101
95
102
<para>
@@ -210,9 +217,7 @@ $ENV{PATH}=$ENV{PATH} . ';c:\some\where\bison\bin';
210
217
Both <productname>Bison</productname> and <productname>Flex</productname>
211
218
are included in the <productname>msys</productname> tool suite, available
212
219
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.
216
221
</para>
217
222
218
223
<para>
@@ -221,9 +226,7 @@ $ENV{PATH}=$ENV{PATH} . ';c:\some\where\bison\bin';
221
226
PATH environment variable in <filename>buildenv.pl</filename> unless
222
227
they are already in PATH. In the case of MinGW, the directory is the
223
228
<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.
227
230
</para>
228
231
229
232
<note>
0 commit comments