glib/win32/vs9/glib-version-paths.vsprops.in
Chun-wei Fan 9aa98db404 Visual Studio builds: Use PythonDir instead of PythonPath
This is to avoid confusion with the PYTHONPATH envvar that is commonly
used to determine where additional Python modules can be loaded,
especially in the case of a MSBuild build.  Note that envvar names are
not case sensitive on Windows in general.
2017-07-13 17:45:44 +08:00

58 lines
1.1 KiB
XML

<?xml version="1.0" encoding="Windows-1252"?>
<VisualStudioPropertySheet
ProjectType="Visual C++"
Version="8.00"
Name="glibversionpathsprops"
>
<UserMacro
Name="VSVer"
Value="9"
/>
<UserMacro
Name="GlibVersion"
Value="@GLIB_VERSION@"
/>
<UserMacro
Name="ApiVersion"
Value="2.0"
/>
<UserMacro
Name="GlibEtcInstallRoot"
Value="..\..\..\vs$(VSVer)\$(PlatformName)"
/>
<UserMacro
Name="CopyDir"
Value="$(GlibEtcInstallRoot)"
/>
<UserMacro
Name="GlibLibtoolCompatibleDllPrefix"
Value="lib"
/>
<UserMacro
Name="GlibLibtoolCompatibleDllSuffix"
Value="-$(ApiVersion)-0"
/>
<UserMacro
Name="GlibSeparateVSDllPrefix"
Value=""
/>
<UserMacro
Name="GlibSeparateVSDllSuffix"
Value="-2-vs$(VSVer)"
/>
<!-- Change these two to GlibLibtoolCompatibleDllPrefix and
GlibLibtoolCompatibleDllSuffix if that is what you want -->
<UserMacro
Name="GlibDllPrefix"
Value="$(GlibSeparateVSDllPrefix)"
/>
<UserMacro
Name="GlibDllSuffix"
Value="$(GlibSeparateVSDllSuffix)"
/>
<UserMacro
Name="PythonDir"
Value="c:\python27"
/>
</VisualStudioPropertySheet>