There are several different ways of building PostgreSQL on

<productname>Windows</productname>. The simplest way to build with

Microsoft tools is to install a supported version of the

<productname>MicrosoftPlatform SDK</productname> and use the included

<productname>MicrosoftWindows SDK</productname> and use the included

compiler. It is also possible to build with the full

<productname>Microsoft Visual C++ 2005or2008</productname>. In some cases

that requires the installation of the <productname>Platform SDK</productname>

<productname>Microsoft Visual C++ 2005, 2008or2010</productname>. In some cases

that requires the installation of the <productname>Windows SDK</productname>

in addition to the compiler.

</para>

<sect1 id="install-windows-full">

<title>Building with <productname>Visual C++</productname> or the

<productname>Platform SDK</productname></title>

<productname>Microsoft Windows SDK</productname></title>

<para>

PostgreSQL can be built using the Visual C++ compiler suite from Microsoft.

These compilers can be either from <productname>Visual Studio</productname>,

<productname>Visual Studio Express</productname> or some versions of the

<productname>Platform SDK</productname>. If you do not already have a

<productname>Microsoft Windows SDK</productname>. If you do not already have a

<productname>Visual Studio</productname> environment set up, the easiest

wayus to use the compilers in the <productname>Platform SDK</productname>,

wayis to use the compilers in the <productname>Windows SDK</productname>,

which is a free download from Microsoft.

</para>

<para>

PostgreSQL supports the compilers from

<productname>Visual Studio 2005</productname> and

<productname>Visual Studio 2008</productname>. When using the Platform SDK

only, or when building for 64-bit Windows, only

<productname>Visual Studio 2008</productname> is supported.

<productname>Visual Studio 2010</productname> is not yet supported.

</para>

<para>

When building using the <productname>Platform SDK</productname>, versions

6.0 to 7.0 of the SDK are supported. Older or newer versions will not work.

In particular, versions from 7.0a and later will not work, since

they include compilers from <productname>Visual Studio 2010</productname>.

PostgreSQL is known to support compilation using the compilers shipped with

<productname>Visual Studio 2005</productname> to

<productname>Visual Studio 2010</productname> (including Express editions),

as well as standalone Windows SDK releases 6.0 to 7.1.

64-bit PostgreSQL builds are only supported with

<productname>Microsoft Windows SDK</productname> version 6.0a and above or

<productname>Visual Studio 2008</productname> and above.

</para>

<para>

<productname>Cygwin</productname> present in your system PATH. Also, make

sure you have all the required Visual C++ tools available in the PATH. In

<productname>Visual Studio</productname>, start the

<application>Visual Studio Command Prompt</application>. In the

<productname>Platform SDK</productname>, start the

<application>CMD shell</application> listed under the SDK on the Start Menu.

<application>Visual Studio Command Prompt</application>.

If you wish to build a 64-bit version, you must use the 64-bit version of

the command, and vice versa.

In the <productname>Microsoft Windows SDK</productname>, start the

<application>CMD shell</application> listed under the SDK on the Start Menu.

In recent SDK versions you can change the targeted CPU architecture by using

the <command>setenv</command> command.

All commands should be run from the <filename>src\tools\msvc</filename>

directory.

</para>

<variablelist>

<varlistentry>

<term><productname>MicrosoftPlatform SDK</productname></term>

<term><productname>MicrosoftWindows SDK</productname></term>

<listitem><para>

It is recommended that you upgrade to the latest supported version

of the <productname>MicrosoftPlatform SDK</productname> (currently

version 7.0), available for download from

of the <productname>MicrosoftWindows SDK</productname> (currently

version 7.1), available for download from

<ulink url="http://www.microsoft.com/downloads/"></>.

</para>

<para>

You must always include the

<application>Windows Headers and Libraries</application> part of the SDK.

If you install the <productname>Platform SDK</productname>

If you install the <productname>Windows SDK</productname>

including the <application>Visual C++ Compilers</application>,

you don't need <productname>Visual Studio</productname> to build.

</para></listitem>

Bison can be downloaded from <ulink url="http://gnuwin32.sourceforge.net"></>.

Flex can be downloaded from

<ulink url="http://www.postgresql.org/ftp/misc/winflex/"></>.

If you are using <productname>msysGit</productname> for accessing the

PostgreSQL <productname>Git</productname> repository you probably already

have recent versions of bison and flex in your <productname>Git</productname>

binary directory.

</para>

<note>

static library to link into an application. For normal use the

<productname>MinGW</productname> or

<productname>Visual Studio</productname> or

<productname>Platform SDK</productname> method is recommended.

<productname>Windows SDK</productname> method is recommended.

</para>

<para>

#defineIPC_STAT 4096

#defineEACCESS 2048

#defineEIDRM 4096

#defineSETALL 8192

#defineGETNCNT 16384

#defineEOPNOTSUPP WSAEOPNOTSUPP

#if_MSC_VER >=1600

#pragma warning(disable:4005)

#defineEMSGSIZE WSAEMSGSIZE

#defineEAFNOSUPPORT WSAEAFNOSUPPORT

#defineEWOULDBLOCK WSAEWOULDBLOCK

#defineEPROTONOSUPPORT WSAEPROTONOSUPPORT

#defineECONNRESET WSAECONNRESET

#defineEINPROGRESS WSAEINPROGRESS

#defineENOBUFS WSAENOBUFS

#defineECONNREFUSED WSAECONNREFUSED

#defineEOPNOTSUPP WSAEOPNOTSUPP

#pragma warning(default:4005)

my$majorver = DetermineMajorVersion();

print"Installing version$majorver for$conf in$target\n";

EnsureDirectories(

$target,'bin','lib','share',

'share/timezonesets','share/extension','share/contrib','doc',

'doc/extension','doc/contrib','symbols','share/tsearch_data'

);

EnsureDirectories($target,'bin','lib','share','share/timezonesets','share/extension',

'share/contrib','doc','doc/extension','doc/contrib','symbols','share/tsearch_data');

CopySolutionOutput($conf,$target);

lcopy($target .'/lib/libpq.dll',$target .'/bin/libpq.dll');

my$rem =qr{Project\("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}"\) = "([^"]+)"};

my$sln = read_file("pgsql.sln") || croak"Could not open pgsql.sln\n";

my$vcproj ='vcproj';

if ($sln =~/Microsoft Visual Studio Solution File, Format Version (\d+)\.\d+/ &&$1 >= 11)

{

$vcproj ='vcxproj';

}

print"Copying build output files...";

while ($sln =~$rem)

{

$sln =~s/$rem//;

my$proj = read_file("$pf.vcproj") || croak"Could not open$pf.vcproj\n";

if ($proj!~qr{ConfigurationType="([^"]+)"})

my$proj = read_file("$pf.$vcproj") || croak"Could not open$pf.$vcproj\n";

if ($vcprojeq'vcproj' &&$proj=~qr{ConfigurationType="([^"]+)"})

{

croak"Could not parse$pf.vcproj\n";

}

if ($1 == 1)

{

$dir ="bin";

$ext ="exe";

if ($1 == 1)

{

$dir ="bin";

$ext ="exe";

}

elsif ($1 == 2)

{

$dir ="lib";

$ext ="dll";

}

{

next;

}

}

elsif ($1 == 2)

elsif ($vcprojeq'vcxproj' &&$proj =~qr{<ConfigurationType>(\w+)</ConfigurationType>})

{

$dir ="lib";

$ext ="dll";

if ($1eq'Application')

{

$dir ="bin";

$ext ="exe";

}

elsif ($1eq'DynamicLibrary')

{

$dir ="lib";

$ext ="dll";

}

{

next;

}

}

{

next;

croak"Could not parse$pf.$vcproj\n";

}

lcopy("$conf\\$pf\\$pf.$ext","$target\\$dir\\$pf.$ext")

|| croak"Could not copy$pf.$ext\n";

$target .'/include/server/',

'src/include/','pg_config.h','pg_config_os.h'

);

CopyFiles('Grammar header',$target .'/include/server/parser/','src/backend/parser/',

'gram.h');

CopyFiles('Grammar header',$target .'/include/server/parser/','src/backend/parser/','gram.h');

CopySetOfFiles('',[glob("src\\include\\*.h") ],$target .'/include/server/');

my$D;

opendir($D,'src/include') || croak"Could not opendir on src/include!\n";