<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.1. Building with Visual C++ or the Microsoft Windows SDK</title><link rel="stylesheet" type="text/css" href="stylesheet.css" /><link rev="made" href="pgsql-docs@lists.postgresql.org" /><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot" /><link rel="prev" href="install-windows.html" title="Chapter 17. Installation from Source Code on Windows" /><link rel="next" href="runtime.html" title="Chapter 18. Server Setup and Operation" /></head><body><div xmlns="http://www.w3.org/TR/xhtml1/transitional" class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="5" align="center">17.1. Building with <span xmlns="http://www.w3.org/1999/xhtml" class="productname">Visual C++</span> or the
<span xmlns="http://www.w3.org/1999/xhtml" class="productname">Microsoft Windows SDK</span></th></tr><tr><td width="10%" align="left"><a accesskey="p" href="install-windows.html" title="Chapter 17. Installation from Source Code on Windows">Prev</a> </td><td width="10%" align="left"><a accesskey="u" href="install-windows.html" title="Chapter 17. Installation from Source Code on Windows">Up</a></td><th width="60%" align="center">Chapter 17. Installation from Source Code on <span xmlns="http://www.w3.org/1999/xhtml" class="productname">Windows</span></th><td width="10%" align="right"><a accesskey="h" href="index.html" title="PostgreSQL 11.5 Documentation">Home</a></td><td width="10%" align="right"> <a accesskey="n" href="runtime.html" title="Chapter 18. Server Setup and Operation">Next</a></td></tr></table><hr></hr></div><div class="sect1" id="INSTALL-WINDOWS-FULL"><div class="titlepage"><div><div><h2 class="title" style="clear: both">17.1. Building with <span class="productname">Visual C++</span> or the
<span class="productname">Microsoft Windows SDK</span></h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="sect2"><a href="install-windows-full.html#id-1.6.4.8.8">17.1.1. Requirements</a></span></dt><dt><span class="sect2"><a href="install-windows-full.html#id-1.6.4.8.9">17.1.2. Special Considerations for 64-bit Windows</a></span></dt><dt><span class="sect2"><a href="install-windows-full.html#id-1.6.4.8.10">17.1.3. Building</a></span></dt><dt><span class="sect2"><a href="install-windows-full.html#id-1.6.4.8.11">17.1.4. Cleaning and Installing</a></span></dt><dt><span class="sect2"><a href="install-windows-full.html#id-1.6.4.8.12">17.1.5. Running the Regression Tests</a></span></dt><dt><span class="sect2"><a href="install-windows-full.html#id-1.6.4.8.13">17.1.6. Building the Documentation</a></span></dt></dl></div><p>
PostgreSQL can be built using the Visual C++ compiler suite from Microsoft.
These compilers can be either from <span class="productname">Visual Studio</span>,
<span class="productname">Visual Studio Express</span> or some versions of the
<span class="productname">Microsoft Windows SDK</span>. If you do not already have a
<span class="productname">Visual Studio</span> environment set up, the easiest
ways are to use the compilers from <span class="productname">Visual Studio Express 2019
for Windows Desktop</span> or those in the <span class="productname">Windows SDK
10</span>, which are both free downloads from Microsoft.
</p><p>
Both 32-bit and 64-bit builds are possible with the Microsoft Compiler suite.
32-bit PostgreSQL builds are possible with
<span class="productname">Visual Studio 2005</span> to
<span class="productname">Visual Studio 2019</span> (including Express editions),
as well as standalone Windows SDK releases 6.0 to 10.
64-bit PostgreSQL builds are supported with
<span class="productname">Microsoft Windows SDK</span> version 6.0a to 10 or
<span class="productname">Visual Studio 2008</span> and above. Compilation
is supported down to <span class="productname">Windows XP</span> and
<span class="productname">Windows Server 2003</span> when building with
<span class="productname">Visual Studio 2005</span> to
<span class="productname">Visual Studio 2013</span>. Building with
<span class="productname">Visual Studio 2015</span> is supported down to
<span class="productname">Windows Vista</span> and <span class="productname">Windows Server 2008</span>.
Building with <span class="productname">Visual Studio 2017</span> to
<span class="productname">Visual Studio 2019</span> is supported
down to <span class="productname">Windows 7 SP1</span> and <span class="productname">Windows Server 2008 R2 SP1</span>.
</p><p>
The tools for building using <span class="productname">Visual C++</span> or
<span class="productname">Platform SDK</span> are in the
<code class="filename">src/tools/msvc</code> directory. When building, make sure
there are no tools from <span class="productname">MinGW</span> or
<span class="productname">Cygwin</span> present in your system PATH. Also, make
sure you have all the required Visual C++ tools available in the PATH. In
<span class="productname">Visual Studio</span>, start the
<span class="application">Visual Studio Command Prompt</span>.
If you wish to build a 64-bit version, you must use the 64-bit version of
the command, and vice versa.
In the <span class="productname">Microsoft Windows SDK</span>, start the
<span class="application">CMD shell</span> listed under the SDK on the Start Menu.
In recent SDK versions you can change the targeted CPU architecture, build
type, and target OS by using the <code class="command">setenv</code> command, e.g.
<code class="command">setenv /x86 /release /xp</code> to target Windows XP or later
with a 32-bit release build. See <code class="command">/?</code> for other options to
<code class="command">setenv</code>. All commands should be run from the
<code class="filename">src\tools\msvc</code> directory.
</p><p>
Before you build, you may need to edit the file <code class="filename">config.pl</code>
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 <code class="filename">config_default.pl</code>,
and then apply any changes from <code class="filename">config.pl</code>. For example,
to specify the location of your <span class="productname">Python</span> installation,
put the following in <code class="filename">config.pl</code>:
</p><pre class="programlisting">
$config->{python} = 'c:\python26';
</pre><p>
You only need to specify those parameters that are different from what's in
<code class="filename">config_default.pl</code>.
</p><p>
If you need to set any other environment variables, create a file called
<code class="filename">buildenv.pl</code> and put the required commands there. For
example, to add the path for bison when it's not in the PATH, create a file
containing:
</p><pre class="programlisting">
$ENV{PATH}=$ENV{PATH} . ';c:\some\where\bison\bin';
</pre><p>
</p><p>
To pass additional command line arguments to the Visual Studio build
command (msbuild or vcbuild):
</p><pre class="programlisting">
$ENV{MSBFLAGS}="/m";
</pre><p>
</p><div class="sect2" id="id-1.6.4.8.8"><div class="titlepage"><div><div><h3 class="title">17.1.1. Requirements</h3></div></div></div><p>
The following additional products are required to build
<span class="productname">PostgreSQL</span>. Use the
<code class="filename">config.pl</code> file to specify which directories the libraries
are available in.
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><span class="productname">Microsoft Windows SDK</span></span></dt><dd><p>
If your build environment doesn't ship with a supported version of the
<span class="productname">Microsoft Windows SDK</span> it
is recommended that you upgrade to the latest version (currently
version 10), available for download from
<a class="ulink" href="https://www.microsoft.com/download" target="_top">https://www.microsoft.com/download</a>.
</p><p>
You must always include the
<span class="application">Windows Headers and Libraries</span> part of the SDK.
If you install a <span class="productname">Windows SDK</span>
including the <span class="application">Visual C++ Compilers</span>,
you don't need <span class="productname">Visual Studio</span> to build.
Note that as of Version 8.0a the Windows SDK no longer ships with a
complete command-line build environment.
</p></dd><dt><span class="term"><span class="productname">ActiveState Perl</span></span></dt><dd><p>
ActiveState Perl is required to run the build generation scripts. MinGW
or Cygwin Perl will not work. It must also be present in the PATH.
Binaries can be downloaded from
<a class="ulink" href="https://www.activestate.com" target="_top">https://www.activestate.com</a>
(Note: version 5.8.3 or later is required,
the free Standard Distribution is sufficient).
</p></dd></dl></div><p>
</p><p>
The following additional products are not required to get started,
but are required to build the complete package. Use the
<code class="filename">config.pl</code> file to specify which directories the libraries
are available in.
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><span class="productname">ActiveState TCL</span></span></dt><dd><p>
Required for building <span class="application">PL/Tcl</span> (Note: version
8.4 is required, the free Standard Distribution is sufficient).
</p></dd><dt><span class="term"><span class="productname">Bison</span> and
<span class="productname">Flex</span></span></dt><dd><p>
<span class="productname">Bison</span> and <span class="productname">Flex</span> are
required to build from Git, but not required when building from a release
file. Only <span class="productname">Bison</span> 1.875 or versions 2.2 and later
will work. <span class="productname">Flex</span> must be version 2.5.31 or later.
</p><p>
Both <span class="productname">Bison</span> and <span class="productname">Flex</span>
are included in the <span class="productname">msys</span> tool suite, available
from <a class="ulink" href="http://www.mingw.org/wiki/MSYS" target="_top">http://www.mingw.org/wiki/MSYS</a> as part of the
<span class="productname">MinGW</span> compiler suite.
</p><p>
You will need to add the directory containing
<code class="filename">flex.exe</code> and <code class="filename">bison.exe</code> to the
PATH environment variable in <code class="filename">buildenv.pl</code> unless
they are already in PATH. In the case of MinGW, the directory is the
<code class="filename">\msys\1.0\bin</code> subdirectory of your MinGW
installation directory.
</p><div class="note"><h3 class="title">Note</h3><p>
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 <code class="filename">C:\Program Files\GnuWin32</code>.
Consider installing into <code class="filename">C:\GnuWin32</code> or use the
NTFS short name path to GnuWin32 in your PATH environment setting
(e.g. <code class="filename">C:\PROGRA~1\GnuWin32</code>).
</p></div><div class="note"><h3 class="title">Note</h3><p>
The obsolete <code class="literal">winflex</code> binaries distributed on the PostgreSQL FTP site
and referenced in older documentation will fail with <span class="quote">“<span class="quote">flex: fatal
internal error, exec failed</span>”</span> on 64-bit Windows hosts. Use Flex from
MSYS instead.
</p></div></dd><dt><span class="term"><span class="productname">Diff</span></span></dt><dd><p>
Diff is required to run the regression tests, and can be downloaded
from <a class="ulink" href="http://gnuwin32.sourceforge.net" target="_top">http://gnuwin32.sourceforge.net</a>.
</p></dd><dt><span class="term"><span class="productname">Gettext</span></span></dt><dd><p>
Gettext is required to build with NLS support, and can be downloaded
from <a class="ulink" href="http://gnuwin32.sourceforge.net" target="_top">http://gnuwin32.sourceforge.net</a>. Note that binaries,
dependencies and developer files are all needed.
</p></dd><dt><span class="term"><span class="productname">MIT Kerberos</span></span></dt><dd><p>
Required for GSSAPI authentication support. MIT Kerberos can be
downloaded from
<a class="ulink" href="http://web.mit.edu/Kerberos/dist/index.html" target="_top">http://web.mit.edu/Kerberos/dist/index.html</a>.
</p></dd><dt><span class="term"><span class="productname">libxml2</span> and
<span class="productname">libxslt</span></span></dt><dd><p>
Required for XML support. Binaries can be downloaded from
<a class="ulink" href="http://zlatkovic.com/pub/libxml" target="_top">http://zlatkovic.com/pub/libxml</a> or source from
<a class="ulink" href="http://xmlsoft.org" target="_top">http://xmlsoft.org</a>. Note that libxml2 requires iconv,
which is available from the same download location.
</p></dd><dt><span class="term"><span class="productname">OpenSSL</span></span></dt><dd><p>
Required for SSL support. Binaries can be downloaded from
<a class="ulink" href="https://slproweb.com/products/Win32OpenSSL.html" target="_top">https://slproweb.com/products/Win32OpenSSL.html</a>
or source from <a class="ulink" href="https://www.openssl.org" target="_top">https://www.openssl.org</a>.
</p></dd><dt><span class="term"><span class="productname">ossp-uuid</span></span></dt><dd><p>
Required for UUID-OSSP support (contrib only). Source can be
downloaded from
<a class="ulink" href="http://www.ossp.org/pkg/lib/uuid/" target="_top">http://www.ossp.org/pkg/lib/uuid/</a>.
</p></dd><dt><span class="term"><span class="productname">Python</span></span></dt><dd><p>
Required for building <span class="application">PL/Python</span>. Binaries can
be downloaded from <a class="ulink" href="https://www.python.org" target="_top">https://www.python.org</a>.
</p></dd><dt><span class="term"><span class="productname">zlib</span></span></dt><dd><p>
Required for compression support in <span class="application">pg_dump</span>
and <span class="application">pg_restore</span>. Binaries can be downloaded
from <a class="ulink" href="http://www.zlib.net" target="_top">http://www.zlib.net</a>.
</p></dd></dl></div><p>
</p></div><div class="sect2" id="id-1.6.4.8.9"><div class="titlepage"><div><div><h3 class="title">17.1.2. Special Considerations for 64-bit Windows</h3></div></div></div><p>
PostgreSQL will only build for the x64 architecture on 64-bit Windows, there
is no support for Itanium processors.
</p><p>
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.
</p><p>
To use a server-side third party library such as <span class="productname">python</span> or
<span class="productname">OpenSSL</span>, this library <span class="emphasis"><em>must</em></span> 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.
</p></div><div class="sect2" id="id-1.6.4.8.10"><div class="titlepage"><div><div><h3 class="title">17.1.3. Building</h3></div></div></div><p>
To build all of PostgreSQL in release configuration (the default), run the
command:
</p><pre class="screen">
<strong class="userinput"><code>build</code></strong>
</pre><p>
To build all of PostgreSQL in debug configuration, run the command:
</p><pre class="screen">
<strong class="userinput"><code>build DEBUG</code></strong>
</pre><p>
To build just a single project, for example psql, run the commands:
</p><pre class="screen">
<strong class="userinput"><code>build psql</code></strong>
<strong class="userinput"><code>build DEBUG psql</code></strong>
</pre><p>
To change the default build configuration to debug, put the following
in the <code class="filename">buildenv.pl</code> file:
</p><pre class="programlisting">
$ENV{CONFIG}="Debug";
</pre><p>
</p><p>
It is also possible to build from inside the Visual Studio GUI. In this
case, you need to run:
</p><pre class="screen">
<strong class="userinput"><code>perl mkvcbuild.pl</code></strong>
</pre><p>
from the command prompt, and then open the generated
<code class="filename">pgsql.sln</code> (in the root directory of the source tree)
in Visual Studio.
</p></div><div class="sect2" id="id-1.6.4.8.11"><div class="titlepage"><div><div><h3 class="title">17.1.4. Cleaning and Installing</h3></div></div></div><p>
Most of the time, the automatic dependency tracking in Visual Studio will
handle changed files. But if there have been large changes, you may need
to clean the installation. To do this, simply run the
<code class="filename">clean.bat</code> command, which will automatically clean out
all generated files. You can also run it with the
<em class="parameter"><code>dist</code></em> parameter, in which case it will behave like
<strong class="userinput"><code>make distclean</code></strong> and remove the flex/bison output files
as well.
</p><p>
By default, all files are written into a subdirectory of the
<code class="filename">debug</code> or <code class="filename">release</code> directories. To
install these files using the standard layout, and also generate the files
required to initialize and use the database, run the command:
</p><pre class="screen">
<strong class="userinput"><code>install c:\destination\directory</code></strong>
</pre><p>
</p><p>
If you want to install only the client applications and
interface libraries, then you can use these commands:
</p><pre class="screen">
<strong class="userinput"><code>install c:\destination\directory client</code></strong>
</pre><p>
</p></div><div class="sect2" id="id-1.6.4.8.12"><div class="titlepage"><div><div><h3 class="title">17.1.5. Running the Regression Tests</h3></div></div></div><p>
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
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
the <code class="filename">buildenv.pl</code> file. To run the tests, run one of
the following commands from the <code class="filename">src\tools\msvc</code>
directory:
</p><pre class="screen">
<strong class="userinput"><code>vcregress check</code></strong>
<strong class="userinput"><code>vcregress installcheck</code></strong>
<strong class="userinput"><code>vcregress plcheck</code></strong>
<strong class="userinput"><code>vcregress contribcheck</code></strong>
<strong class="userinput"><code>vcregress modulescheck</code></strong>
<strong class="userinput"><code>vcregress ecpgcheck</code></strong>
<strong class="userinput"><code>vcregress isolationcheck</code></strong>
<strong class="userinput"><code>vcregress bincheck</code></strong>
<strong class="userinput"><code>vcregress recoverycheck</code></strong>
<strong class="userinput"><code>vcregress upgradecheck</code></strong>
</pre><p>
To change the schedule used (default is parallel), append it to the
command line like:
</p><pre class="screen">
<strong class="userinput"><code>vcregress check serial</code></strong>
</pre><p>
For more information about the regression tests, see
<a class="xref" href="regress.html" title="Chapter 33. Regression Tests">Chapter 33</a>.
</p><p>
Running the regression tests on client programs, with
<code class="command">vcregress bincheck</code>, or on recovery tests, with
<code class="command">vcregress recoverycheck</code>, requires an additional Perl module
to be installed:
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><span class="productname">IPC::Run</span></span></dt><dd><p>
As of this writing, <code class="literal">IPC::Run</code> is not included in the
ActiveState Perl installation, nor in the ActiveState Perl Package
Manager (PPM) library. To install, download the
<code class="filename">IPC-Run-<version>.tar.gz</code> source archive from CPAN,
at <a class="ulink" href="https://metacpan.org/release/IPC-Run" target="_top">https://metacpan.org/release/IPC-Run</a>, and
uncompress. Edit the <code class="filename">buildenv.pl</code> file, and add a PERL5LIB
variable to point to the <code class="filename">lib</code> subdirectory from the
extracted archive. For example:
</p><pre class="programlisting">
$ENV{PERL5LIB}=$ENV{PERL5LIB} . ';c:\IPC-Run-0.94\lib';
</pre><p>
</p></dd></dl></div><p>
</p></div><div class="sect2" id="id-1.6.4.8.13"><div class="titlepage"><div><div><h3 class="title">17.1.6. Building the Documentation</h3></div></div></div><p>
Building the PostgreSQL documentation in HTML format requires several tools
and files. Create a root directory for all these files, and store them
in the subdirectories in the list below.
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">OpenJade 1.3.1-2</span></dt><dd><p>
Download from
<a class="ulink" href="https://sourceforge.net/projects/openjade/files/openjade/1.3.1/openjade-1_3_1-2-bin.zip/download" target="_top">https://sourceforge.net/projects/openjade/files/openjade/1.3.1/openjade-1_3_1-2-bin.zip/download</a>
and uncompress in the subdirectory <code class="filename">openjade-1.3.1</code>.
</p></dd><dt><span class="term">DocBook DTD 4.2</span></dt><dd><p>
Download from
<a class="ulink" href="https://www.oasis-open.org/docbook/sgml/4.2/docbook-4.2.zip" target="_top">https://www.oasis-open.org/docbook/sgml/4.2/docbook-4.2.zip</a>
and uncompress in the subdirectory <code class="filename">docbook</code>.
</p></dd><dt><span class="term">ISO character entities</span></dt><dd><p>
Download from
<a class="ulink" href="https://www.oasis-open.org/cover/ISOEnts.zip" target="_top">https://www.oasis-open.org/cover/ISOEnts.zip</a> and
uncompress in the subdirectory <code class="filename">docbook</code>.
</p></dd></dl></div><p>
Edit the <code class="filename">buildenv.pl</code> file, and add a variable for the
location of the root directory, for example:
</p><pre class="programlisting">
$ENV{DOCROOT}='c:\docbook';
</pre><p>
To build the documentation, run the command
<code class="filename">builddoc.bat</code>. Note that this will actually run the
build twice, in order to generate the indexes. The generated HTML files
will be in <code class="filename">doc\src\sgml</code>.
</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="install-windows.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="install-windows.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="runtime.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 17. Installation from Source Code on <span class="productname">Windows</span> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 18. Server Setup and Operation</td></tr></table></div></body></html>
