There are several different ways of building PostgreSQL on
Windows. The simplest way to build with
- Microsoft tools is to install
Visual Studio Express 2015+ Microsoft tools is to install
Visual Studio Express 2017 for Windows Desktop and use the included
compiler. It is also possible to build with the full
-
Microsoft Visual C++ 2005 to 2015.
+
Microsoft Visual C++ 2005 to 2017.
In some cases that requires the installation of the
Windows SDK in addition to the compiler.
Visual Studio Express or some versions of the
Microsoft Windows SDK. If you do not already have a
Visual Studio environment set up, the easiest
- ways are to use the compilers from
Visual Studio Express 2015+ ways are to use the compilers from
Visual Studio Express 2017 for Windows Desktop or those in the
Windows SDK- 7.1, which are both free downloads from Microsoft.
+ 8.1, which are both free downloads from Microsoft.
Both 32-bit and 64-bit builds are possible with the Microsoft Compiler suite.
32-bit PostgreSQL builds are possible with
-
Visual Studio 2015 (including Express editions),
- as well as standalone Windows SDK releases 6.0 to 7.1.
+
Visual Studio 2017 (including Express editions),
+ as well as standalone Windows SDK releases 6.0 to 8.1.
64-bit PostgreSQL builds are supported with
-
Microsoft Windows SDK version 6.0a to
7.1 or
+
Microsoft Windows SDK version 6.0a to
8.1 or
Visual Studio 2008 and above. Compilation
is supported down to
Windows XP and
Windows Server 2003 when building with
Visual Studio 2013. Building with
Visual Studio 2015 is supported down to
Windows Vista and Windows Server 2008.
+ Building with
Visual Studio 2017 is supported
+ down to
Windows 7 SP1 and Windows Server 2008 R2 SP1.
return $self;
}
+package VC2017Project;
+
+#
+# Package that encapsulates a Visual C++ 2017 project file
+#
+
+use strict;
+use warnings;
+use base qw(VC2012Project);
+
+sub new
+{
+ my $classname = shift;
+ my $self = $classname->SUPER::_new(@_);
+ bless($self, $classname);
+
+ $self->{vcver} = '15.00';
+ $self->{PlatformToolset} = 'v141';
+ $self->{ToolsVersion} = '15.0';
+
+ return $self;
+}
+
1;
==========
This directory contains the tools required to build PostgreSQL using
-Microsoft Visual Studio 2005 - 2011. This builds the whole backend, not just
+Microsoft Visual Studio 2005 - 2017. This builds the whole backend, not just
the libpq frontend library. For more information, see the documentation
chapter "Installation on Windows" and the description below.
(Mkvcbuild.pm) which creates the Visual Studio project and solution files.
It does this by using VSObjectFactory::CreateSolution to create an object
implementing the Solution interface (this could be either a VS2005Solution,
-a VS2008Solution, a VS2010Solution or a VS2012Solution, all in Solution.pm,
-depending on the user's build environment) and adding objects implementing
-the corresponding Project interface (VC2005Project or VC2008Project from
-VCBuildProject.pm or VC2010Project or VC2012Project from MSBuildProject.pm)
-to it.
+a VS2008Solution, a VS2010Solution or a VS2012Solution or a VS2013Solution,
+or a VS2015Solution or a VS2017Solution, all in Solution.pm, depending on
+the user's build environment) and adding objects implementing the corresponding
+Project interface (VC2005Project or VC2008Project from VCBuildProject.pm or
+VC2010Project or VC2012Project or VC2013Project or VC2015Project or VC2017Project
+from MSBuildProject.pm) to it.
When Solution::Save is called, the implementations of Solution and Project
save their content in the appropriate format.
The final step of starting the appropriate build program (msbuild or vcbuild)
return $self;
}
+package VS2017Solution;
+
+#
+# Package that encapsulates a Visual Studio 2017 solution file
+#
+
+use Carp;
+use strict;
+use warnings;
+use base qw(Solution);
+
+sub new
+{
+ my $classname = shift;
+ my $self = $classname->SUPER::_new(@_);
+ bless($self, $classname);
+
+ $self->{solutionFileVersion} = '12.00';
+ $self->{vcver} = '15.00';
+ $self->{visualStudioName} = 'Visual Studio 2017';
+ $self->{VisualStudioVersion} = '15.0.26730.3';
+ $self->{MinimumVisualStudioVersion} = '10.0.40219.1';
+
+ return $self;
+}
+
sub GetAdditionalHeaders
{
my ($self, $f) = @_;
{
return new VS2015Solution(@_);
}
+ # visual 2017 hasn't changed the nmake version to 15, so adjust the check to support it.
+ elsif (($visualStudioVersion ge '14.10') or ($visualStudioVersion eq '15.00'))
+ {
+ return new VS2017Solution(@_);
+ }
else
{
+ croak $visualStudioVersion;
croak "The requested Visual Studio version is not supported.";
}
}
{
return new VC2015Project(@_);
}
+ # visual 2017 hasn't changed the nmake version to 15, so adjust the check to support it.
+ elsif (($visualStudioVersion ge '14.10') or ($visualStudioVersion eq '15.00'))
+ {
+ return new VC2017Project(@_);
+ }
else
{
+ croak $visualStudioVersion;
croak "The requested Visual Studio version is not supported.";
}
}
sub _GetVisualStudioVersion
{
my ($major, $minor) = @_;
+ # visual 2017 hasn't changed the nmake version to 15, so still using the older version for comparison.
if ($major > 14)
{
carp
projects / postgresql.git / commitdiff