Commit 7d64d109 authored by Chun-wei Fan's avatar Chun-wei Fan

MSVC 201x builds: Allow different Python versions per toolset

Use conditionals to select the Python installation, so that we can more
stick to the default Visual Studio versions used to compile each
official Python releases more closely.

This means by default:
-2010/2012/2013 builds use Python 3.4.x, which is built with 2010
-2015/2017 builds use Python 3.6.x, which is built with 2015
parent a00e7ed3
......@@ -12,7 +12,11 @@
<GlibSeparateVSDllSuffix>-2-vs$(VSVer)</GlibSeparateVSDllSuffix>
<GlibDllPrefix>$(GlibSeparateVSDllPrefix)</GlibDllPrefix>
<GlibDllSuffix>$(GlibSeparateVSDllSuffix)</GlibDllSuffix>
<PythonPath>c:\python27</PythonPath>
<PythonPath Condition="'$(VisualStudioVersion)' == '10.0'">c:\python34</PythonPath>
<PythonPath Condition="'$(VisualStudioVersion)' == '11.0'">c:\python34</PythonPath>
<PythonPath Condition="'$(VisualStudioVersion)' == '12.0'">c:\python34</PythonPath>
<PythonPath Condition="'$(VisualStudioVersion)' == '14.0'">c:\python36</PythonPath>
<PythonPath Condition="'$(VisualStudioVersion)' == '15.0'">c:\python36</PythonPath>
</PropertyGroup>
<PropertyGroup>
<_PropertySheetDisplayName>glibversionpathsprops</_PropertySheetDisplayName>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment