2010-09-23 23:44:22 +02:00
|
|
|
<!-- doc/src/sgml/install-windows.sgml -->
|
2003-09-29 20:18:35 +02:00
|
|
|
|
2010-09-23 23:44:22 +02:00
|
|
|
<chapter id="install-windows">
|
2009-01-09 14:37:18 +01:00
|
|
|
<title>Installation from Source Code on <productname>Windows</productname></title>
|
1999-01-07 03:59:45 +01:00
|
|
|
|
2001-05-13 00:51:36 +02:00
|
|
|
<indexterm>
|
|
|
|
<primary>installation</primary>
|
|
|
|
<secondary>on Windows</secondary>
|
|
|
|
</indexterm>
|
|
|
|
|
2000-12-21 23:30:39 +01:00
|
|
|
<para>
|
2010-11-23 21:27:50 +01:00
|
|
|
It is recommended that most users download the binary distribution for
|
2013-04-10 21:37:49 +02:00
|
|
|
Windows, available as a graphical installer package
|
2007-03-13 17:03:36 +01:00
|
|
|
from the <productname>PostgreSQL</productname> website. Building from source
|
|
|
|
is only intended for people developing <productname>PostgreSQL</productname>
|
|
|
|
or extensions.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
There are several different ways of building PostgreSQL on
|
2010-01-12 21:13:32 +01:00
|
|
|
<productname>Windows</productname>. The simplest way to build with
|
2016-04-29 13:59:47 +02:00
|
|
|
Microsoft tools is to install <productname>Visual Studio Express 2015
|
2013-02-06 20:52:29 +01:00
|
|
|
for Windows Desktop</productname> and use the included
|
2010-01-12 21:13:32 +01:00
|
|
|
compiler. It is also possible to build with the full
|
2016-04-29 13:59:47 +02:00
|
|
|
<productname>Microsoft Visual C++ 2005 to 2015</productname>.
|
2014-01-26 15:49:10 +01:00
|
|
|
In some cases that requires the installation of the
|
|
|
|
<productname>Windows SDK</productname> in addition to the compiler.
|
2010-01-12 21:13:32 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
It is also possible to build PostgreSQL using the GNU compiler tools
|
|
|
|
provided by <productname>MinGW</productname>, or using
|
|
|
|
<productname>Cygwin</productname> for older versions of
|
|
|
|
<productname>Windows</productname>.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Finally, the client access library
|
2007-03-13 17:03:36 +01:00
|
|
|
(<application>libpq</application>) can be built using
|
2010-11-23 21:27:50 +01:00
|
|
|
<productname>Visual C++ 7.1</productname> or
|
2007-03-13 17:03:36 +01:00
|
|
|
<productname>Borland C++</productname> for compatibility with statically
|
|
|
|
linked applications built using these tools.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Building using <productname>MinGW</productname> or
|
|
|
|
<productname>Cygwin</productname> uses the normal build system, see
|
2008-11-21 17:46:19 +01:00
|
|
|
<xref linkend="installation"> and the specific notes in
|
|
|
|
<xref linkend="installation-notes-mingw"> and <xref linkend="installation-notes-cygwin">.
|
2011-01-31 19:40:45 +01:00
|
|
|
To produce native 64 bit binaries in these environments, use the tools from
|
2011-02-10 10:47:32 +01:00
|
|
|
<productname>MinGW-w64</productname>. These tools can also be used to
|
2011-08-07 15:11:55 +02:00
|
|
|
cross-compile for 32 bit and 64 bit <productname>Windows</productname>
|
|
|
|
targets on other hosts, such as <productname>Linux</productname> and
|
Refer to OS X as "macOS", except for the port name which is still "darwin".
We weren't terribly consistent about whether to call Apple's OS "OS X"
or "Mac OS X", and the former is probably confusing to people who aren't
Apple users. Now that Apple has rebranded it "macOS", follow their lead
to establish a consistent naming pattern. Also, avoid the use of the
ancient project name "Darwin", except as the port code name which does not
seem desirable to change. (In short, this patch touches documentation and
comments, but no actual code.)
I didn't touch contrib/start-scripts/osx/, either. I suspect those are
obsolete and due for a rewrite, anyway.
I dithered about whether to apply this edit to old release notes, but
those were responsible for quite a lot of the inconsistencies, so I ended
up changing them too. Anyway, Apple's being ahistorical about this,
so why shouldn't we be?
2016-09-25 21:40:57 +02:00
|
|
|
<productname>macOS</productname>.
|
2011-01-31 19:40:45 +01:00
|
|
|
<productname>Cygwin</productname> is not recommended for running a
|
|
|
|
production server, and it should only be used for running on
|
|
|
|
older versions of <productname>Windows</productname> where
|
2010-11-23 21:27:50 +01:00
|
|
|
the native build does not work, such as
|
2011-01-31 19:40:45 +01:00
|
|
|
<productname>Windows 98</productname>. The official
|
2010-01-12 21:13:32 +01:00
|
|
|
binaries are built using <productname>Visual Studio</productname>.
|
2007-03-13 17:03:36 +01:00
|
|
|
</para>
|
|
|
|
|
2011-01-31 19:40:45 +01:00
|
|
|
<para>
|
2011-08-07 15:11:55 +02:00
|
|
|
Native builds of <application>psql</application> don't support command
|
2011-01-31 19:40:45 +01:00
|
|
|
line editing. The <productname>Cygwin</productname> build does support
|
|
|
|
command line editing, so it should be used where psql is needed for
|
|
|
|
interactive use on <productname>Windows</productname>.
|
|
|
|
</para>
|
|
|
|
|
2010-09-23 23:44:22 +02:00
|
|
|
<sect1 id="install-windows-full">
|
2010-01-12 21:13:32 +01:00
|
|
|
<title>Building with <productname>Visual C++</productname> or the
|
2012-01-03 14:44:26 +01:00
|
|
|
<productname>Microsoft Windows SDK</productname></title>
|
2010-01-12 21:13:32 +01:00
|
|
|
|
|
|
|
<para>
|
|
|
|
PostgreSQL can be built using the Visual C++ compiler suite from Microsoft.
|
|
|
|
These compilers can be either from <productname>Visual Studio</productname>,
|
2011-04-15 15:00:42 +02:00
|
|
|
<productname>Visual Studio Express</productname> or some versions of the
|
2012-01-03 14:44:26 +01:00
|
|
|
<productname>Microsoft Windows SDK</productname>. If you do not already have a
|
2010-01-12 21:13:32 +01:00
|
|
|
<productname>Visual Studio</productname> environment set up, the easiest
|
2016-04-29 13:59:47 +02:00
|
|
|
ways are to use the compilers from <productname>Visual Studio Express 2015
|
2014-01-26 15:49:10 +01:00
|
|
|
for Windows Desktop</productname> or those in the <productname>Windows SDK
|
|
|
|
7.1</productname>, which are both free downloads from Microsoft.
|
2010-01-12 21:13:32 +01:00
|
|
|
</para>
|
2007-03-13 17:03:36 +01:00
|
|
|
|
|
|
|
<para>
|
2016-04-29 13:59:47 +02:00
|
|
|
Both 32-bit and 64-bit builds are possible with the Microsoft Compiler suite.
|
2016-07-08 15:26:53 +02:00
|
|
|
32-bit PostgreSQL builds are possible with
|
2012-01-03 14:44:26 +01:00
|
|
|
<productname>Visual Studio 2005</productname> to
|
2016-04-29 13:59:47 +02:00
|
|
|
<productname>Visual Studio 2015</productname> (including Express editions),
|
2012-01-03 14:44:26 +01:00
|
|
|
as well as standalone Windows SDK releases 6.0 to 7.1.
|
2016-04-29 13:59:47 +02:00
|
|
|
64-bit PostgreSQL builds are supported with
|
2013-02-06 20:52:29 +01:00
|
|
|
<productname>Microsoft Windows SDK</productname> version 6.0a to 7.1 or
|
2016-04-29 13:59:47 +02:00
|
|
|
<productname>Visual Studio 2008</productname> and above. Compilation
|
|
|
|
is supported down to <productname>Windows XP</productname> and
|
|
|
|
<productname>Windows Server 2003</> when building with
|
|
|
|
<productname>Visual Studio 2005</> to
|
|
|
|
<productname>Visual Studio 2013</productname>. Building with
|
|
|
|
<productname>Visual Studio 2015</productname> is supported down to
|
|
|
|
<productname>Windows Vista</> and <productname>Windows Server 2008</>.
|
2010-01-12 21:13:32 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2013-01-01 17:09:31 +01:00
|
|
|
The tools for building using <productname>Visual C++</productname> or
|
|
|
|
<productname>Platform SDK</productname> are in the
|
|
|
|
<filename>src/tools/msvc</filename> directory. When building, make sure
|
|
|
|
there are no tools from <productname>MinGW</productname> or
|
2007-03-13 17:03:36 +01:00
|
|
|
<productname>Cygwin</productname> present in your system PATH. Also, make
|
2010-01-12 21:13:32 +01:00
|
|
|
sure you have all the required Visual C++ tools available in the PATH. In
|
|
|
|
<productname>Visual Studio</productname>, start the
|
2012-01-03 14:44:26 +01:00
|
|
|
<application>Visual Studio Command Prompt</application>.
|
2010-01-12 21:13:32 +01:00
|
|
|
If you wish to build a 64-bit version, you must use the 64-bit version of
|
|
|
|
the command, and vice versa.
|
2012-01-03 14:44:26 +01:00
|
|
|
In the <productname>Microsoft Windows SDK</productname>, start the
|
|
|
|
<application>CMD shell</application> listed under the SDK on the Start Menu.
|
2013-01-01 17:09:31 +01:00
|
|
|
In recent SDK versions you can change the targeted CPU architecture, build
|
|
|
|
type, and target OS by using the <command>setenv</command> command, e.g.
|
|
|
|
<command>setenv /x86 /release /xp</command> to target Windows XP or later
|
|
|
|
with a 32-bit release build. See <command>/?</command> for other options to
|
|
|
|
<command>setenv</command>. All commands should be run from the
|
|
|
|
<filename>src\tools\msvc</filename> directory.
|
2010-01-12 21:13:32 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Before you build, you may need to edit the file <filename>config.pl</filename>
|
|
|
|
to reflect any configuration options you want to change, or the paths to
|
|
|
|
any third party libraries to use. The complete configuration is determined
|
|
|
|
by first reading and parsing the file <filename>config_default.pl</filename>,
|
|
|
|
and then apply any changes from <filename>config.pl</filename>. For example,
|
|
|
|
to specify the location of your <productname>Python</productname> installation,
|
|
|
|
put the following in <filename>config.pl</filename>:
|
2010-07-29 21:34:41 +02:00
|
|
|
<programlisting>
|
|
|
|
$config->{python} = 'c:\python26';
|
|
|
|
</programlisting>
|
2010-01-12 21:13:32 +01:00
|
|
|
You only need to specify those parameters that are different from what's in
|
|
|
|
<filename>config_default.pl</filename>.
|
2007-03-13 17:03:36 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
If you need to set any other environment variables, create a file called
|
2007-12-19 13:29:36 +01:00
|
|
|
<filename>buildenv.pl</filename> and put the required commands there. For
|
2007-03-13 17:03:36 +01:00
|
|
|
example, to add the path for bison when it's not in the PATH, create a file
|
|
|
|
containing:
|
2010-07-29 21:34:41 +02:00
|
|
|
<programlisting>
|
|
|
|
$ENV{PATH}=$ENV{PATH} . ';c:\some\where\bison\bin';
|
|
|
|
</programlisting>
|
2000-12-21 23:30:39 +01:00
|
|
|
</para>
|
1999-01-07 03:59:45 +01:00
|
|
|
|
2016-09-08 07:42:09 +02:00
|
|
|
<para>
|
|
|
|
To pass additional command line arguments to the Visual Studio build
|
|
|
|
command (msbuild or vcbuild):
|
|
|
|
<programlisting>
|
|
|
|
$ENV{MSBFLAGS}="/m";
|
|
|
|
</programlisting>
|
|
|
|
</para>
|
|
|
|
|
2007-03-13 17:03:36 +01:00
|
|
|
<sect2>
|
|
|
|
<title>Requirements</title>
|
|
|
|
<para>
|
2010-01-12 21:13:32 +01:00
|
|
|
The following additional products are required to build
|
|
|
|
<productname>PostgreSQL</productname>. Use the
|
2008-07-29 17:23:44 +02:00
|
|
|
<filename>config.pl</filename> file to specify which directories the libraries
|
2007-03-14 01:15:26 +01:00
|
|
|
are available in.
|
2007-03-13 17:03:36 +01:00
|
|
|
|
|
|
|
<variablelist>
|
2010-01-12 21:13:32 +01:00
|
|
|
<varlistentry>
|
2012-01-03 14:44:26 +01:00
|
|
|
<term><productname>Microsoft Windows SDK</productname></term>
|
2010-01-12 21:13:32 +01:00
|
|
|
<listitem><para>
|
2013-02-06 20:52:29 +01:00
|
|
|
If your build environment doesn't ship with a supported version of the
|
|
|
|
<productname>Microsoft Windows SDK</productname> it
|
|
|
|
is recommended that you upgrade to the latest version (currently
|
2012-01-03 14:44:26 +01:00
|
|
|
version 7.1), available for download from
|
2011-05-30 20:46:14 +02:00
|
|
|
<ulink url="http://www.microsoft.com/downloads/"></>.
|
2010-01-12 21:13:32 +01:00
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
You must always include the
|
|
|
|
<application>Windows Headers and Libraries</application> part of the SDK.
|
2013-02-06 20:52:29 +01:00
|
|
|
If you install a <productname>Windows SDK</productname>
|
2010-01-12 21:13:32 +01:00
|
|
|
including the <application>Visual C++ Compilers</application>,
|
|
|
|
you don't need <productname>Visual Studio</productname> to build.
|
2013-02-06 20:52:29 +01:00
|
|
|
Note that as of Version 8.0a the Windows SDK no longer ships with a
|
|
|
|
complete command-line build environment.
|
2010-01-12 21:13:32 +01:00
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2007-03-13 17:03:36 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><productname>ActiveState Perl</productname></term>
|
|
|
|
<listitem><para>
|
2007-03-14 01:15:26 +01:00
|
|
|
ActiveState Perl is required to run the build generation scripts. MinGW
|
2007-11-28 16:42:31 +01:00
|
|
|
or Cygwin Perl will not work. It must also be present in the PATH.
|
2007-03-14 01:15:26 +01:00
|
|
|
Binaries can be downloaded from
|
2011-07-04 21:30:27 +02:00
|
|
|
<ulink url="http://www.activestate.com"></> (Note: version 5.8 or later is required,
|
2008-07-29 17:17:27 +02:00
|
|
|
the free Standard Distribution is sufficient).
|
2007-03-14 01:15:26 +01:00
|
|
|
</para></listitem>
|
2007-03-13 17:03:36 +01:00
|
|
|
</varlistentry>
|
|
|
|
|
2010-01-12 21:13:32 +01:00
|
|
|
</variablelist>
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
The following additional products are not required to get started,
|
|
|
|
but are required to build the complete package. Use the
|
|
|
|
<filename>config.pl</filename> file to specify which directories the libraries
|
|
|
|
are available in.
|
|
|
|
|
|
|
|
<variablelist>
|
2007-03-13 17:03:36 +01:00
|
|
|
<varlistentry>
|
2007-03-14 01:15:26 +01:00
|
|
|
<term><productname>ActiveState TCL</productname></term>
|
2007-03-13 17:03:36 +01:00
|
|
|
<listitem><para>
|
2008-07-29 17:17:27 +02:00
|
|
|
Required for building <application>PL/TCL</application> (Note: version
|
|
|
|
8.4 is required, the free Standard Distribution is sufficient).
|
2007-03-14 01:15:26 +01:00
|
|
|
</para></listitem>
|
2007-03-13 17:03:36 +01:00
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><productname>Bison</productname> and
|
2007-03-14 01:15:26 +01:00
|
|
|
<productname>Flex</productname></term>
|
2013-01-01 17:09:31 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
<productname>Bison</productname> and <productname>Flex</productname> are
|
|
|
|
required to build from Git, but not required when building from a release
|
|
|
|
file. Only <productname>Bison</productname> 1.875 or versions 2.2 and later
|
|
|
|
will work. <productname>Flex</productname> must be version 2.5.31 or later.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Both <productname>Bison</productname> and <productname>Flex</productname>
|
|
|
|
are included in the <productname>msys</productname> tool suite, available
|
|
|
|
from <ulink url="http://www.mingw.org/wiki/MSYS"></> as part of the
|
2016-04-29 13:59:47 +02:00
|
|
|
<productname>MinGW</productname> compiler suite.
|
2013-01-01 17:09:31 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
You will need to add the directory containing
|
|
|
|
<filename>flex.exe</filename> and <filename>bison.exe</filename> to the
|
|
|
|
PATH environment variable in <filename>buildenv.pl</filename> unless
|
|
|
|
they are already in PATH. In the case of MinGW, the directory is the
|
|
|
|
<filename>\msys\1.0\bin</filename> subdirectory of your MinGW
|
2016-04-29 13:59:47 +02:00
|
|
|
installation directory.
|
2011-04-15 15:27:02 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<note>
|
|
|
|
<para>
|
|
|
|
The Bison distribution from GnuWin32 appears to have a bug that
|
|
|
|
causes Bison to malfunction when installed in a directory with
|
|
|
|
spaces in the name, such as the default location on English
|
|
|
|
installations <filename>C:\Program Files\GnuWin32</filename>.
|
2013-01-01 17:09:31 +01:00
|
|
|
Consider installing into <filename>C:\GnuWin32</filename> or use the
|
2013-05-21 03:13:13 +02:00
|
|
|
NTFS short name path to GnuWin32 in your PATH environment setting
|
2013-01-01 17:09:31 +01:00
|
|
|
(e.g. <filename>C:\PROGRA~1\GnuWin32</filename>).
|
|
|
|
</para>
|
|
|
|
</note>
|
|
|
|
|
|
|
|
<note>
|
|
|
|
<para>
|
2016-04-16 18:49:36 +02:00
|
|
|
The obsolete <literal>winflex</literal> binaries distributed on the PostgreSQL FTP site
|
|
|
|
and referenced in older documentation will fail with <quote>flex: fatal
|
|
|
|
internal error, exec failed</quote> on 64-bit Windows hosts. Use Flex from
|
|
|
|
MSYS instead.
|
2011-04-15 15:27:02 +02:00
|
|
|
</para>
|
|
|
|
</note>
|
|
|
|
</listitem>
|
2007-03-13 17:03:36 +01:00
|
|
|
</varlistentry>
|
|
|
|
|
2007-03-17 15:30:00 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><productname>Diff</productname></term>
|
|
|
|
<listitem><para>
|
|
|
|
Diff is required to run the regression tests, and can be downloaded
|
|
|
|
from <ulink url="http://gnuwin32.sourceforge.net"></>.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2007-03-24 23:16:49 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><productname>Gettext</productname></term>
|
|
|
|
<listitem><para>
|
|
|
|
Gettext is required to build with NLS support, and can be downloaded
|
|
|
|
from <ulink url="http://gnuwin32.sourceforge.net"></>. Note that binaries,
|
|
|
|
dependencies and developer files are all needed.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2007-03-13 17:03:36 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><productname>MIT Kerberos</productname></term>
|
|
|
|
<listitem><para>
|
2014-01-15 17:24:01 +01:00
|
|
|
Required for GSSAPI authentication support. MIT Kerberos can be
|
2010-11-23 21:27:50 +01:00
|
|
|
downloaded from
|
2007-03-14 01:15:26 +01:00
|
|
|
<ulink url="http://web.mit.edu/Kerberos/dist/index.html"></>.
|
|
|
|
</para></listitem>
|
2007-03-13 17:03:36 +01:00
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><productname>libxml2</productname> and
|
2007-03-14 01:15:26 +01:00
|
|
|
<productname>libxslt</productname></term>
|
2007-03-13 17:03:36 +01:00
|
|
|
<listitem><para>
|
|
|
|
Required for XML support. Binaries can be downloaded from
|
2007-03-14 01:15:26 +01:00
|
|
|
<ulink url="http://zlatkovic.com/pub/libxml"></> or source from
|
|
|
|
<ulink url="http://xmlsoft.org"></>. Note that libxml2 requires iconv,
|
|
|
|
which is available from the same download location.
|
|
|
|
</para></listitem>
|
2007-03-13 17:03:36 +01:00
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><productname>openssl</productname></term>
|
|
|
|
<listitem><para>
|
|
|
|
Required for SSL support. Binaries can be downloaded from
|
|
|
|
<ulink url="http://www.slproweb.com/products/Win32OpenSSL.html"></>
|
2007-03-14 01:15:26 +01:00
|
|
|
or source from <ulink url="http://www.openssl.org"></>.
|
|
|
|
</para></listitem>
|
2007-03-13 17:03:36 +01:00
|
|
|
</varlistentry>
|
|
|
|
|
2008-02-28 13:17:59 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><productname>ossp-uuid</productname></term>
|
|
|
|
<listitem><para>
|
2010-11-23 21:27:50 +01:00
|
|
|
Required for UUID-OSSP support (contrib only). Source can be
|
2008-02-28 13:17:59 +01:00
|
|
|
downloaded from
|
|
|
|
<ulink url="http://www.ossp.org/pkg/lib/uuid/"></>.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2007-03-13 17:03:36 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><productname>Python</productname></term>
|
|
|
|
<listitem><para>
|
|
|
|
Required for building <application>PL/Python</application>. Binaries can
|
2007-03-14 01:15:26 +01:00
|
|
|
be downloaded from <ulink url="http://www.python.org"></>.
|
|
|
|
</para></listitem>
|
2007-03-13 17:03:36 +01:00
|
|
|
</varlistentry>
|
|
|
|
|
2007-03-14 01:15:26 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><productname>zlib</productname></term>
|
2007-03-13 17:03:36 +01:00
|
|
|
<listitem><para>
|
2007-03-14 01:15:26 +01:00
|
|
|
Required for compression support in <application>pg_dump</application>
|
|
|
|
and <application>pg_restore</application>. Binaries can be downloaded
|
|
|
|
from <ulink url="http://www.zlib.net"></>.
|
|
|
|
</para></listitem>
|
2007-03-13 17:03:36 +01:00
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
</variablelist>
|
|
|
|
</para>
|
|
|
|
</sect2>
|
|
|
|
|
2010-01-12 21:13:32 +01:00
|
|
|
<sect2>
|
2011-01-29 19:00:18 +01:00
|
|
|
<title>Special Considerations for 64-bit Windows</title>
|
2010-01-12 21:13:32 +01:00
|
|
|
|
|
|
|
<para>
|
|
|
|
PostgreSQL will only build for the x64 architecture on 64-bit Windows, there
|
|
|
|
is no support for Itanium processors.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Mixing 32- and 64-bit versions in the same build tree is not supported.
|
|
|
|
The build system will automatically detect if it's running in a 32- or
|
|
|
|
64-bit environment, and build PostgreSQL accordingly. For this reason, it
|
|
|
|
is important to start the correct command prompt before building.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
To use a server-side third party library such as <productname>python</> or
|
|
|
|
<productname>openssl</>, this library <emphasis>must</emphasis> also be
|
|
|
|
64-bit. There is no support for loading a 32-bit library in a 64-bit
|
|
|
|
server. Several of the third party libraries that PostgreSQL supports may
|
|
|
|
only be available in 32-bit versions, in which case they cannot be used with
|
|
|
|
64-bit PostgreSQL.
|
|
|
|
</para>
|
|
|
|
</sect2>
|
|
|
|
|
2007-03-13 17:03:36 +01:00
|
|
|
<sect2>
|
|
|
|
<title>Building</title>
|
|
|
|
|
|
|
|
<para>
|
2007-04-18 12:14:06 +02:00
|
|
|
To build all of PostgreSQL in release configuration (the default), run the
|
2007-03-14 01:15:26 +01:00
|
|
|
command:
|
2010-07-29 21:34:41 +02:00
|
|
|
<screen>
|
|
|
|
<userinput>build</userinput>
|
|
|
|
</screen>
|
2007-04-18 12:14:06 +02:00
|
|
|
To build all of PostgreSQL in debug configuration, run the command:
|
2010-07-29 21:34:41 +02:00
|
|
|
<screen>
|
|
|
|
<userinput>build DEBUG</userinput>
|
|
|
|
</screen>
|
2007-03-13 17:03:36 +01:00
|
|
|
To build just a single project, for example psql, run the commands:
|
2010-07-29 21:34:41 +02:00
|
|
|
<screen>
|
|
|
|
<userinput>build psql</userinput>
|
|
|
|
<userinput>build DEBUG psql</userinput>
|
|
|
|
</screen>
|
2007-04-18 12:14:06 +02:00
|
|
|
To change the default build configuration to debug, put the following
|
2007-12-19 13:29:36 +01:00
|
|
|
in the <filename>buildenv.pl</filename> file:
|
2010-07-29 21:34:41 +02:00
|
|
|
<programlisting>
|
|
|
|
$ENV{CONFIG}="Debug";
|
|
|
|
</programlisting>
|
2007-03-13 17:03:36 +01:00
|
|
|
</para>
|
|
|
|
|
2000-12-21 23:30:39 +01:00
|
|
|
<para>
|
2007-03-13 17:03:36 +01:00
|
|
|
It is also possible to build from inside the Visual Studio GUI. In this
|
2007-03-14 01:15:26 +01:00
|
|
|
case, you need to run:
|
2010-07-29 21:34:41 +02:00
|
|
|
<screen>
|
|
|
|
<userinput>perl mkvcbuild.pl</userinput>
|
|
|
|
</screen>
|
2007-03-13 17:03:36 +01:00
|
|
|
from the command prompt, and then open the generated
|
2007-03-14 01:15:26 +01:00
|
|
|
<filename>pgsql.sln</filename> (in the root directory of the source tree)
|
|
|
|
in Visual Studio.
|
2000-12-21 23:30:39 +01:00
|
|
|
</para>
|
2007-03-13 17:03:36 +01:00
|
|
|
</sect2>
|
|
|
|
|
|
|
|
<sect2>
|
2011-01-29 19:00:18 +01:00
|
|
|
<title>Cleaning and Installing</title>
|
2007-03-13 17:03:36 +01:00
|
|
|
|
|
|
|
<para>
|
|
|
|
Most of the time, the automatic dependency tracking in Visual Studio will
|
2007-03-14 01:15:26 +01:00
|
|
|
handle changed files. But if there have been large changes, you may need
|
|
|
|
to clean the installation. To do this, simply run the
|
|
|
|
<filename>clean.bat</filename> command, which will automatically clean out
|
2008-03-14 18:28:23 +01:00
|
|
|
all generated files. You can also run it with the
|
2008-02-06 16:13:25 +01:00
|
|
|
<parameter>dist</parameter> parameter, in which case it will behave like
|
|
|
|
<userinput>make distclean</userinput> and remove the flex/bison output files
|
|
|
|
as well.
|
2007-03-13 17:03:36 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
By default, all files are written into a subdirectory of the
|
2007-03-14 01:15:26 +01:00
|
|
|
<filename>debug</filename> or <filename>release</filename> directories. To
|
|
|
|
install these files using the standard layout, and also generate the files
|
|
|
|
required to initialize and use the database, run the command:
|
2010-07-29 21:34:41 +02:00
|
|
|
<screen>
|
|
|
|
<userinput>install c:\destination\directory</userinput>
|
2014-01-26 23:03:13 +01:00
|
|
|
</screen>
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
If you want to install only the client applications and
|
|
|
|
interface libraries, then you can use these commands:
|
|
|
|
<screen>
|
|
|
|
<userinput>install c:\destination\directory client</userinput>
|
2010-07-29 21:34:41 +02:00
|
|
|
</screen>
|
2007-03-13 17:03:36 +01:00
|
|
|
</para>
|
|
|
|
</sect2>
|
|
|
|
|
2007-03-21 20:22:52 +01:00
|
|
|
<sect2>
|
2011-01-29 19:00:18 +01:00
|
|
|
<title>Running the Regression Tests</title>
|
2007-03-21 20:22:52 +01:00
|
|
|
|
|
|
|
<para>
|
|
|
|
To run the regression tests, make sure you have completed the build of all
|
|
|
|
required parts first. Also, make sure that the DLLs required to load all
|
2007-11-28 16:42:31 +01:00
|
|
|
parts of the system (such as the Perl and Python DLLs for the procedural
|
|
|
|
languages) are present in the system path. If they are not, set it through
|
2007-12-19 13:29:36 +01:00
|
|
|
the <filename>buildenv.pl</filename> file. To run the tests, run one of
|
2007-03-21 20:22:52 +01:00
|
|
|
the following commands from the <filename>src\tools\msvc</filename>
|
|
|
|
directory:
|
2010-07-29 21:34:41 +02:00
|
|
|
<screen>
|
|
|
|
<userinput>vcregress check</userinput>
|
|
|
|
<userinput>vcregress installcheck</userinput>
|
|
|
|
<userinput>vcregress plcheck</userinput>
|
|
|
|
<userinput>vcregress contribcheck</userinput>
|
2015-04-17 04:39:52 +02:00
|
|
|
<userinput>vcregress modulescheck</userinput>
|
2014-12-17 11:14:34 +01:00
|
|
|
<userinput>vcregress ecpgcheck</userinput>
|
|
|
|
<userinput>vcregress isolationcheck</userinput>
|
2015-11-19 05:32:16 +01:00
|
|
|
<userinput>vcregress bincheck</userinput>
|
2016-02-26 20:13:30 +01:00
|
|
|
<userinput>vcregress recoverycheck</userinput>
|
2014-12-17 11:14:34 +01:00
|
|
|
<userinput>vcregress upgradecheck</userinput>
|
2010-07-29 21:34:41 +02:00
|
|
|
</screen>
|
2007-03-21 20:22:52 +01:00
|
|
|
|
2010-02-03 18:25:06 +01:00
|
|
|
To change the schedule used (default is parallel), append it to the
|
2007-11-28 16:42:31 +01:00
|
|
|
command line like:
|
2010-07-29 21:34:41 +02:00
|
|
|
<screen>
|
|
|
|
<userinput>vcregress check serial</userinput>
|
|
|
|
</screen>
|
2007-03-21 20:22:52 +01:00
|
|
|
|
|
|
|
For more information about the regression tests, see
|
|
|
|
<xref linkend="regress">.
|
|
|
|
</para>
|
2015-07-29 18:17:02 +02:00
|
|
|
|
|
|
|
<para>
|
2016-02-29 22:16:59 +01:00
|
|
|
Running the regression tests on client programs, with
|
|
|
|
<command>vcregress bincheck</>, or on recovery tests, with
|
2016-04-02 03:53:10 +02:00
|
|
|
<command>vcregress recoverycheck</>, requires an additional Perl module
|
2016-02-29 22:16:59 +01:00
|
|
|
to be installed:
|
2015-07-29 18:17:02 +02:00
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term><productname>IPC::Run</productname></term>
|
|
|
|
<listitem><para>
|
|
|
|
As of this writing, <literal>IPC::Run</> is not included in the
|
|
|
|
ActiveState Perl installation, nor in the ActiveState Perl Package
|
|
|
|
Manager (PPM) library. To install, download the
|
|
|
|
<filename>IPC-Run-<version>.tar.gz</> source archive from CPAN,
|
|
|
|
at <ulink url="http://search.cpan.org/dist/IPC-Run/"></>, and
|
|
|
|
uncompress. Edit the <filename>buildenv.pl</> file, and add a PERL5LIB
|
|
|
|
variable to point to the <filename>lib</> subdirectory from the
|
|
|
|
extracted archive. For example:
|
|
|
|
<programlisting>
|
|
|
|
$ENV{PERL5LIB}=$ENV{PERL5LIB} . ';c:\IPC-Run-0.94\lib';
|
|
|
|
</programlisting>
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
|
|
|
</para>
|
2007-03-21 20:22:52 +01:00
|
|
|
</sect2>
|
|
|
|
|
2007-03-13 17:03:36 +01:00
|
|
|
<sect2>
|
2011-01-29 19:00:18 +01:00
|
|
|
<title>Building the Documentation</title>
|
2007-03-13 17:03:36 +01:00
|
|
|
|
|
|
|
<para>
|
|
|
|
Building the PostgreSQL documentation in HTML format requires several tools
|
2007-03-14 01:15:26 +01:00
|
|
|
and files. Create a root directory for all these files, and store them
|
|
|
|
in the subdirectories in the list below.
|
2007-03-13 17:03:36 +01:00
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term>OpenJade 1.3.1-2</term>
|
|
|
|
<listitem><para>
|
|
|
|
Download from
|
2010-03-17 18:12:31 +01:00
|
|
|
<ulink url="http://sourceforge.net/projects/openjade/files/openjade/1.3.1/openjade-1_3_1-2-bin.zip/download"></>
|
2007-03-14 01:15:26 +01:00
|
|
|
and uncompress in the subdirectory <filename>openjade-1.3.1</filename>.
|
2007-03-13 17:03:36 +01:00
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>DocBook DTD 4.2</term>
|
|
|
|
<listitem><para>
|
|
|
|
Download from
|
2007-03-14 01:15:26 +01:00
|
|
|
<ulink url="http://www.oasis-open.org/docbook/sgml/4.2/docbook-4.2.zip"></>
|
|
|
|
and uncompress in the subdirectory <filename>docbook</filename>.
|
2007-03-13 17:03:36 +01:00
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2007-11-28 16:42:31 +01:00
|
|
|
<term>DocBook DSSSL 1.79</term>
|
2007-03-13 17:03:36 +01:00
|
|
|
<listitem><para>
|
|
|
|
Download from
|
2010-03-17 18:12:31 +01:00
|
|
|
<ulink url="http://sourceforge.net/projects/docbook/files/docbook-dsssl/1.79/docbook-dsssl-1.79.zip/download"></>
|
2007-03-13 17:03:36 +01:00
|
|
|
and uncompress in the subdirectory
|
2007-03-14 01:15:26 +01:00
|
|
|
<filename>docbook-dsssl-1.79</filename>.
|
2007-03-13 17:03:36 +01:00
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>ISO character entities</term>
|
|
|
|
<listitem><para>
|
|
|
|
Download from
|
2007-03-14 01:15:26 +01:00
|
|
|
<ulink url="http://www.oasis-open.org/cover/ISOEnts.zip"></> and
|
|
|
|
uncompress in the subdirectory <filename>docbook</filename>.
|
2007-03-13 17:03:36 +01:00
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
2007-12-19 13:29:36 +01:00
|
|
|
Edit the <filename>buildenv.pl</filename> file, and add a variable for the
|
2007-03-14 01:15:26 +01:00
|
|
|
location of the root directory, for example:
|
2010-07-29 21:34:41 +02:00
|
|
|
<programlisting>
|
|
|
|
$ENV{DOCROOT}='c:\docbook';
|
|
|
|
</programlisting>
|
2007-03-13 17:03:36 +01:00
|
|
|
To build the documentation, run the command
|
2007-03-14 01:15:26 +01:00
|
|
|
<filename>builddoc.bat</filename>. Note that this will actually run the
|
|
|
|
build twice, in order to generate the indexes. The generated HTML files
|
|
|
|
will be in <filename>doc\src\sgml</filename>.
|
2007-03-13 17:03:36 +01:00
|
|
|
</para>
|
|
|
|
</sect2>
|
|
|
|
|
|
|
|
</sect1>
|
|
|
|
|
2010-09-23 23:44:22 +02:00
|
|
|
<sect1 id="install-windows-libpq">
|
2007-03-13 17:03:36 +01:00
|
|
|
<title>Building <application>libpq</application> with
|
|
|
|
<productname>Visual C++</productname> or
|
|
|
|
<productname>Borland C++</productname></title>
|
1999-01-07 03:59:45 +01:00
|
|
|
|
2000-12-21 23:30:39 +01:00
|
|
|
<para>
|
2010-01-12 21:13:32 +01:00
|
|
|
Using <productname>Visual C++ 7.1-9.0</productname> or
|
2007-03-13 17:03:36 +01:00
|
|
|
<productname>Borland C++</productname> to build libpq is only recommended
|
|
|
|
if you need a version with different debug/release flags, or if you need a
|
|
|
|
static library to link into an application. For normal use the
|
|
|
|
<productname>MinGW</productname> or
|
2010-01-12 21:13:32 +01:00
|
|
|
<productname>Visual Studio</productname> or
|
2012-01-03 14:44:26 +01:00
|
|
|
<productname>Windows SDK</productname> method is recommended.
|
2007-03-13 17:03:36 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
To build the <application>libpq</application> client library using
|
2007-08-03 12:47:11 +02:00
|
|
|
<productname>Visual Studio 7.1 or later</productname>, change into the
|
2009-04-27 18:27:36 +02:00
|
|
|
<filename>src</filename> directory and type the command:
|
2000-12-21 23:30:39 +01:00
|
|
|
<screen>
|
|
|
|
<userinput>nmake /f win32.mak</userinput>
|
|
|
|
</screen>
|
|
|
|
</para>
|
2007-04-18 15:50:09 +02:00
|
|
|
<para>
|
|
|
|
To build a 64-bit version of the <application>libpq</application>
|
|
|
|
client library using <productname>Visual Studio 8.0 or
|
|
|
|
later</productname>, change into the <filename>src</filename>
|
2009-04-27 18:27:36 +02:00
|
|
|
directory and type in the command:
|
2007-04-18 15:50:09 +02:00
|
|
|
<screen>
|
|
|
|
<userinput>nmake /f win32.mak CPU=AMD64</userinput>
|
|
|
|
</screen>
|
|
|
|
See the <filename>win32.mak</filename> file for further details
|
|
|
|
about supported variables.
|
|
|
|
</para>
|
1999-01-07 03:59:45 +01:00
|
|
|
|
2004-09-27 21:43:17 +02:00
|
|
|
<para>
|
2007-03-13 17:03:36 +01:00
|
|
|
To build the <application>libpq</application> client library using
|
|
|
|
<productname>Borland C++</productname>, change into the
|
2009-04-27 18:27:36 +02:00
|
|
|
<filename>src</filename> directory and type the command:
|
2004-09-27 21:43:17 +02:00
|
|
|
<screen>
|
2005-05-11 17:10:20 +02:00
|
|
|
<userinput>make -N -DCFG=Release /f bcc32.mak</userinput>
|
2004-09-27 21:43:17 +02:00
|
|
|
</screen>
|
|
|
|
</para>
|
|
|
|
|
2007-03-13 17:03:36 +01:00
|
|
|
<sect2>
|
2011-01-29 19:00:18 +01:00
|
|
|
<title>Generated Files</title>
|
2000-12-21 23:30:39 +01:00
|
|
|
<para>
|
|
|
|
The following files will be built:
|
1999-01-07 03:59:45 +01:00
|
|
|
|
2000-12-21 23:30:39 +01:00
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term><filename>interfaces\libpq\Release\libpq.dll</filename></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
The dynamically linkable frontend library
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2010-11-23 21:27:50 +01:00
|
|
|
|
2000-12-21 23:30:39 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><filename>interfaces\libpq\Release\libpqdll.lib</filename></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
Import library to link your programs to <filename>libpq.dll</filename>
|
2000-12-21 23:30:39 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
1999-01-07 03:59:45 +01:00
|
|
|
|
2000-12-21 23:30:39 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><filename>interfaces\libpq\Release\libpq.lib</filename></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2004-12-27 21:13:48 +01:00
|
|
|
Static version of the frontend library
|
2000-12-21 23:30:39 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
1999-01-07 03:59:45 +01:00
|
|
|
|
2000-12-21 23:30:39 +01:00
|
|
|
</variablelist>
|
|
|
|
</para>
|
1999-01-07 03:59:45 +01:00
|
|
|
|
2000-12-21 23:30:39 +01:00
|
|
|
<para>
|
2007-02-02 17:10:08 +01:00
|
|
|
Normally you do not need to install any of the client files. You should
|
|
|
|
place the <filename>libpq.dll</filename> file in the same directory
|
2007-03-13 17:03:36 +01:00
|
|
|
as your applications executable file. Do not install
|
2010-02-03 18:25:06 +01:00
|
|
|
<filename>libpq.dll</filename> into your <filename>Windows</>,
|
|
|
|
<filename>System</> or <filename>System32</> directory unless
|
|
|
|
absolutely necessary.
|
|
|
|
If this file is installed using a setup program, then it should
|
2000-12-21 23:30:39 +01:00
|
|
|
be installed with version checking using the
|
|
|
|
<symbol>VERSIONINFO</symbol> resource included in the file, to
|
|
|
|
ensure that a newer version of the library is not overwritten.
|
|
|
|
</para>
|
1999-01-07 03:59:45 +01:00
|
|
|
|
2000-12-21 23:30:39 +01:00
|
|
|
<para>
|
2007-03-13 17:03:36 +01:00
|
|
|
If you are planning to do development using <application>libpq</application>
|
2004-09-27 21:43:17 +02:00
|
|
|
on this machine, you will have to add the
|
|
|
|
<filename>src\include</filename> and
|
|
|
|
<filename>src\interfaces\libpq</filename> subdirectories of the source
|
2004-12-27 00:06:56 +01:00
|
|
|
tree to the include path in your compiler's settings.
|
2000-12-21 23:30:39 +01:00
|
|
|
</para>
|
1999-01-07 03:59:45 +01:00
|
|
|
|
2000-12-21 23:30:39 +01:00
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
To use the library, you must add the
|
2000-12-21 23:30:39 +01:00
|
|
|
<filename>libpqdll.lib</filename> file to your project. (In Visual
|
2001-11-28 21:49:10 +01:00
|
|
|
C++, just right-click on the project and choose to add it.)
|
2000-12-21 23:30:39 +01:00
|
|
|
</para>
|
2007-03-13 17:03:36 +01:00
|
|
|
</sect2>
|
|
|
|
</sect1>
|
2000-12-21 23:30:39 +01:00
|
|
|
</chapter>
|