|
20 | 20 | There are several different ways of building PostgreSQL on
|
21 | 21 | <productname>Windows</productname>. The simplest way to build with
|
22 | 22 | Microsoft tools is to install a supported version of the
|
23 |
| - <productname>Microsoft Platform SDK</productname> and use the included |
| 23 | + <productname>Microsoft Windows SDK</productname> and use the included |
24 | 24 | compiler. It is also possible to build with the full
|
25 |
| - <productname>Microsoft Visual C++ 2005 or 2008</productname>. In some cases |
26 |
| - that requires the installation of the <productname>Platform SDK</productname> |
| 25 | + <productname>Microsoft Visual C++ 2005, 2008 or 2010</productname>. In some cases |
| 26 | + that requires the installation of the <productname>Windows SDK</productname> |
27 | 27 | in addition to the compiler.
|
28 | 28 | </para>
|
29 | 29 |
|
|
69 | 69 |
|
70 | 70 | <sect1 id="install-windows-full">
|
71 | 71 | <title>Building with <productname>Visual C++</productname> or the
|
72 |
| - <productname>Platform SDK</productname></title> |
| 72 | + <productname>Microsoft Windows SDK</productname></title> |
73 | 73 |
|
74 | 74 | <para>
|
75 | 75 | PostgreSQL can be built using the Visual C++ compiler suite from Microsoft.
|
76 | 76 | These compilers can be either from <productname>Visual Studio</productname>,
|
77 | 77 | <productname>Visual Studio Express</productname> or some versions of the
|
78 |
| - <productname>Platform SDK</productname>. If you do not already have a |
| 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 |
| - way us to use the compilers in the <productname>Platform SDK</productname>, |
| 80 | + way is to use the compilers in the <productname>Windows SDK</productname>, |
81 | 81 | which is a free download from Microsoft.
|
82 | 82 | </para>
|
83 | 83 |
|
84 | 84 | <para>
|
85 |
| - PostgreSQL supports the compilers from |
86 |
| - <productname>Visual Studio 2005</productname> and |
87 |
| - <productname>Visual Studio 2008</productname>. When using the Platform SDK |
88 |
| - only, or when building for 64-bit Windows, only |
89 |
| - <productname>Visual Studio 2008</productname> is supported. |
90 |
| - <productname>Visual Studio 2010</productname> is not yet supported. |
91 |
| - </para> |
92 |
| - |
93 |
| - <para> |
94 |
| - When building using the <productname>Platform SDK</productname>, versions |
95 |
| - 6.0 to 7.0 of the SDK are supported. Older or newer versions will not work. |
96 |
| - In particular, versions from 7.0a and later will not work, since |
97 |
| - they include compilers from <productname>Visual Studio 2010</productname>. |
| 85 | + PostgreSQL is known to support compilation using the compilers shipped with |
| 86 | + <productname>Visual Studio 2005</productname> to |
| 87 | + <productname>Visual Studio 2010</productname> (including Express editions), |
| 88 | + as well as standalone Windows SDK releases 6.0 to 7.1. |
| 89 | + 64-bit PostgreSQL builds are only supported with |
| 90 | + <productname>Microsoft Windows SDK</productname> version 6.0a and above or |
| 91 | + <productname>Visual Studio 2008</productname> and above. |
98 | 92 | </para>
|
99 | 93 |
|
100 | 94 | <para>
|
|
104 | 98 | <productname>Cygwin</productname> present in your system PATH. Also, make
|
105 | 99 | sure you have all the required Visual C++ tools available in the PATH. In
|
106 | 100 | <productname>Visual Studio</productname>, start the
|
107 |
| - <application>Visual Studio Command Prompt</application>. In the |
108 |
| - <productname>Platform SDK</productname>, start the |
109 |
| - <application>CMD shell</application> listed under the SDK on the Start Menu. |
| 101 | + <application>Visual Studio Command Prompt</application>. |
110 | 102 | If you wish to build a 64-bit version, you must use the 64-bit version of
|
111 | 103 | the command, and vice versa.
|
| 104 | + In the <productname>Microsoft Windows SDK</productname>, start the |
| 105 | + <application>CMD shell</application> listed under the SDK on the Start Menu. |
| 106 | + In recent SDK versions you can change the targeted CPU architecture by using |
| 107 | + the <command>setenv</command> command. |
112 | 108 | All commands should be run from the <filename>src\tools\msvc</filename>
|
113 | 109 | directory.
|
114 | 110 | </para>
|
@@ -148,17 +144,17 @@ $ENV{PATH}=$ENV{PATH} . ';c:\some\where\bison\bin';
|
148 | 144 |
|
149 | 145 | <variablelist>
|
150 | 146 | <varlistentry>
|
151 |
| - <term><productname>Microsoft Platform SDK</productname></term> |
| 147 | + <term><productname>Microsoft Windows SDK</productname></term> |
152 | 148 | <listitem><para>
|
153 | 149 | It is recommended that you upgrade to the latest supported version
|
154 |
| - of the <productname>Microsoft Platform SDK</productname> (currently |
155 |
| - version 7.0), available for download from |
| 150 | + of the <productname>Microsoft Windows SDK</productname> (currently |
| 151 | + version 7.1), available for download from |
156 | 152 | <ulink url="http://www.microsoft.com/downloads/"></>.
|
157 | 153 | </para>
|
158 | 154 | <para>
|
159 | 155 | You must always include the
|
160 | 156 | <application>Windows Headers and Libraries</application> part of the SDK.
|
161 |
| - If you install the <productname>Platform SDK</productname> |
| 157 | + If you install the <productname>Windows SDK</productname> |
162 | 158 | including the <application>Visual C++ Compilers</application>,
|
163 | 159 | you don't need <productname>Visual Studio</productname> to build.
|
164 | 160 | </para></listitem>
|
@@ -202,6 +198,10 @@ $ENV{PATH}=$ENV{PATH} . ';c:\some\where\bison\bin';
|
202 | 198 | Bison can be downloaded from <ulink url="http://gnuwin32.sourceforge.net"></>.
|
203 | 199 | Flex can be downloaded from
|
204 | 200 | <ulink url="http://www.postgresql.org/ftp/misc/winflex/"></>.
|
| 201 | + If you are using <productname>msysGit</productname> for accessing the |
| 202 | + PostgreSQL <productname>Git</productname> repository you probably already |
| 203 | + have recent versions of bison and flex in your <productname>Git</productname> |
| 204 | + binary directory. |
205 | 205 | </para>
|
206 | 206 |
|
207 | 207 | <note>
|
@@ -479,7 +479,7 @@ $ENV{DOCROOT}='c:\docbook';
|
479 | 479 | static library to link into an application. For normal use the
|
480 | 480 | <productname>MinGW</productname> or
|
481 | 481 | <productname>Visual Studio</productname> or
|
482 |
| - <productname>Platform SDK</productname> method is recommended. |
| 482 | + <productname>Windows SDK</productname> method is recommended. |
483 | 483 | </para>
|
484 | 484 |
|
485 | 485 | <para>
|
|
0 commit comments