Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Scripts to build PostgreSQL and its dependencies on Windows automatically
Perl PowerShell Shell
Tree: 958502043e

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.


These scripts create a PostgreSQL build environment for Windows, and build

They're for NMake, the Microsoft version of make that uses cmd.exe. It comes
with Visual Studio. Yes, that's horrid, but it's better than trying to disentangle
the environment of mingw from that of Visual Studio.

You will require installs of ActiveState Perl, ActiveState TCL,
Python 2, MinGW, git (from, and the Microsoft SDK 7.1 to use these
scripts. Instructions on unattended installs for these tools are coming shortly;
just need to copy them from another machine.

Download Windows SDK 7.1

You can download the SDK from: (web installer)
or (offline installers ISOs).

If using the offline installer, get GRMSDKX_EN_DVD.iso for x64 or 
GRMSDK_EN_DVD.iso for x86. You don't need to burn a CD to install it, 
see below for instructions.

You must already have .NET 4 client profile installed to be able to run the 
Windows SDK offline installer. It's installed by default on Windows 7 and
Win2k8 R2 but must be installed manually for older platforms. Get it here:

Download required tools

Some of this will be automated later, but for now you must download the following
required tools. Don't install them; see below for that.

All these instructions assume you're on a 64-bit windows install. If you're on 32-bit, don't
bother downloading the 64-bit installers and omit all steps that refer to them. These instructions
and scripts are NOT TESTED on 32-bit windows, only on 64-bit Windows 7 and Windows Server 2008 R2.

* ActiveState TCL x64 and x86 from
* ActiveState Perl x86 and x64 from
* python 2.7 and 3.3, both in x86 and x64 versions from
* mingw-get-inst from
* git from
* 7-zip from

You need MinGW even for MSVC builds because you need the "flex" executable
from it to build on x64; the version provided on the PostgreSQL site doesn't
run on win64. These scripts also use bison, wget and touch from mingw. All 
these tools come with msysgit too, so a future version may support using
msysgit instead of MinGW.

I also recommend:
* notepad++ from http://

Install the tools

Open a command prompt and cd to the location you downloaded all the above tools to.

Now use the following commands to install the tools. On Windows the command prompt
doesn't wait until a spawned command completes; you can use "start /WAIT" to launch
them and wait, but it won't work with all installers.

You will need to adjust the file names to reflect the exact files you downloaded.

If you're on a 32-bit platform, omit the lines for 64-bit programs and for Perl, use 
PERL_PATH=Yes PERL_EXT=Yes for the 32-bit version since you aren't installing the 64-bit

	start /wait mingw-get-inst-20120426.exe /silent
	c:\MinGW\bin\mingw-get.exe install msys-flex msys-bison g++ gdb mingw32-make msys-base
	start /wait msiexec /i 7z920-x64.msi /qb /passive /norestart
	start /wait Git-1.8.0-preview20121022.exe /silent
	start /wait msiexec /i ActivePerl- /qb /passive PERL_PATH=Yes PERL_EXT=Yes
	start /wait msiexec /i ActivePerl- /qb /passive PERL_PATH=No PERL_EXT=No
	start /wait ActiveTcl8. --directory %SystemDrive%\TCL_85_x86
	start /wait ActiveTcl8. --directory %SystemDrive%\TCL_85_x64
	start /wait msiexec /i python-2.7.3.amd64.msi /qb /passive TARGETDIR=%SystemDrive%\Python27_x64 ALLUSERS=1
	start /wait msiexec /i python-2.7.3.msi /qb /passive TARGETDIR=%SystemDrive%\Python27_x86 ALLUSERS=1
	start /wait msiexec /i python-3.3.0.amd64.msi /qb /passive TARGETDIR=%SystemDrive%\Python33_x64 ALLUSERS=1
	start /wait msiexec /i python-3.3.0.msi /qb /passive TARGETDIR=%SystemDrive%\Python33_x64 ALLUSERS=1
If you downloaded the offline install ISO for the Windows SDK, you can install it with:

	"%PROGRAMFILES%\7-Zip\7z.exe" x -owinsdk GRMSDKX_EN_DVD.iso
	start /wait winsdk\setup.exe -q -params:ADDLOCAL=ALL
	rd /s /q winsdk
(Change GRMSDKX_EN_DVD.iso to GRMSDK_EN_DVD.iso if you're on x64) 

Optionally also install notepad++:

	start /wait npp.6.2.2.Installer.exe /S

Configure the build

Copy settings-template.mak to settings.mak and edit it to reflect your
environment. You can pass the settings on the command line instead, but
currently an empty settings.mak is still required. See settings-defaults.mak
for what you can override.

There are two build modes offered; you must pick whether you want the build
scripts to manage the PostgreSQL sources trees for you by checking them out
from git, or whether you want to manage them yourself. These modes do not
affect libraries, only management of the PostgreSQL sources.

In either case, you must set LIBDIR to the absolute path you want to put
the dependencies that the build scripts manage for you, eg:


Anything inside LIBDIR will be deleted by "nmake really-clean"

Automatic PostgreSQL source trees - USE_GIT

If you set USE_GIT and specify where to put the source trees (PGDIR), where to
find a PostgreSQL git mirror (PG_GIT_URL), what branch to check out (PG_BRANCH)
and the location of the git executable (GIT), the build scripts will manage
your builds for you under PGDIR. Eg:

	GIT=c:\Program Files (x86)\Git\bin\git.exe

Anything inside PGDIR will be deleted by "nmake really-clean". The source tree will be
reset using "git clean -fdx" when you "nmake clean" or "nmake postgresql-clean", so don't
do work in the script-managed PostgreSQL trees; either push to a branch and have the tools
build the branch, or manually manage the source tree (see below).

Builds will go in different locations based on their settings - /x86 vs /x64,
/release vs /debug, SDK version, target OS, and Pg branch. For example,
REL9_2_STABLE built for /x86 /release /xp built with Windows SDK 7.1 with PGDIR
set to c:\postgresql-build will go in:


As cloning Pg from scratch takes time, I recommend cloning a bare copy of the Pg repo *outside* LIBDIR and PGDIR, eg:

	git clone --bare --mirror git:// d:\postgresql-git

and specifying the path to it as PG_GIT_URL:


Manually managed PostgreSQL source trees - set PGBUILDDIR

If you're developing PostgreSQL in an existing working tree or you're using
these scripts for a buildfarm / continuous integration setup, you or some other
tools might be managing your git checkouts, or you could even be working from
source tarballs.  In that case you won't want the build scripts messing around
with git.

You can still use these scripts to manage your library dependencies and to
generate and for you if you're working in a manually
managed source tree. Just leave USE_GIT unset, and set PGBUILDDIR to the
location of your source tree.

For example:

	nmake /f d:\pg_build_win PGBUILDDIR=d:\my-postgresql-dev-tree

The scripts won't use git and you don't need it installed. In this mode, "nmake
postgresql-clean" and "nmake clean" will use "src\tools\msvc\clean.bat dist" to
clean the source tree, rather than using git.

You still need a settings.mak, but if you set LIBDIR on the command line too it
can be an empty file.

(Optional) Download library source archives

The build tools will use wget to download the source archives into LIBDIR\pkg
for you if it can't find them.

If you like, you can create LIBDIR\pkg and copy the source archives from
somewhere yourself for offline use. The filenames the build scripts look
for are specified in settings-default.mak and can be overridden in settings.mak.

Be warned that "nmake really-clean" will delete LIBDIR and its contents,
including any source packages you put there.
Set up your Visual Studio or Windows SDK environment for the build target you want.
Either use the Start menu option to launch a suitable prompt if you want the default
settings, or preferably open a new ordinary Command Prompt and use SetEnv.cmd
(SDK) or vcvars.bat (Studio) to set the environment up.

For windows SDK 7.1 32-bit release builds you'd use:

    "c:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.Cmd" /x86 /release /xp
For options:

    "c:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.Cmd" /?

The main options are "/x86" vs "/x64" and "/Debug" vs "/Release".
You probably want to pass "/xp" for 32-bit builds and "/2008" for 64-bit builds.


In a command prompt that's had its environment set up as per "SET UP
VISUAL STUDIO ENVIRONMENT", do a full build with:

    nmake /f pg_build_win\Makefile postgresql

Supported targets are:

* postgresql: Build PostgreSQL and its dependencies
* postgresql-check: Run the test suite
* postgresql-clean: Clean postgresql working tree, leave libraries alone


If you want to build individual libraries, each library Makefile
has "libname" and "libname-clean" targets, eg:

* zlib
* zlib-clean


* clean - remove built libraries and clean PostgreSQL working tree
* really-clean: Remove built libraries and downloaded files, delete PostgreSQL checkout and working tree


Compiling PostgreSQL from source on Windows:
Windows SDK unattended:
ActivePerl unattended:
ActiveTCL unattended:
Python unattended:
Something went wrong with that request. Please try again.