AuroraMiddleware/gtk
1
0
Fork 1
mirror of https://gitlab.gnome.org/GNOME/gtk.git synced 2024-12-28 14:31:10 +00:00
Code Issues Projects Releases Wiki Activity
1cc5cf3797
gtk/build/win32/vs10/gtk-version-paths.props.in

59 lines
2.2 KiB
Plaintext
Raw Normal View History

MSVC Projects: Use UNIX Line endings ...for all files except the README.txt and the .sln files, which have to have DOS/Windows line endings. This makes application of patches, when applicable, easier.
2013-12-04 00:51:39 +00:00
<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup Label="UserMacros">
<VSVer>10</VSVer>
<GlibEtcInstallRoot>$(SolutionDir)\..\..\..\..\vs$(VSVer)\$(Platform)</GlibEtcInstallRoot>
<CopyDir>..\..\..\..\vs$(VSVer)\$(Platform)</CopyDir>
<ApiVersion>3.0</ApiVersion>
MSVC Build Files: Use Real GTK+ Version Make the Visual C++-related build files contain the actual GTK+ version, by generating them during the configure stage and dist'ing them in the release tarballs. This is especially important for builds of introspection files, as one may need to look at the release version of GTK+ in those files.
2014-08-07 15:11:34 +00:00
<GtkVersion>@GTK_VERSION@</GtkVersion>
MSVC Projects: Use UNIX Line endings ...for all files except the README.txt and the .sln files, which have to have DOS/Windows line endings. This makes application of patches, when applicable, easier.
2013-12-04 00:51:39 +00:00
<GtkLibtoolCompatibleDllPrefix>lib</GtkLibtoolCompatibleDllPrefix>
<GtkLibtoolCompatibleDllSuffix>-$(ApiVersion)-0</GtkLibtoolCompatibleDllSuffix>
<GtkSeparateVSDllPrefix />
<GtkSeparateVSDllSuffix>-3-vs$(VSVer)</GtkSeparateVSDllSuffix>
<GtkDllPrefix>$(GtkSeparateVSDllPrefix)</GtkDllPrefix>
<GtkDllSuffix>$(GtkSeparateVSDllSuffix)</GtkDllSuffix>
Make Visual Studio Build Process A Bit Simpler Add some flexibility in the property sheets for one building GTK+ that it also searches for a settable installation path of Python, in addition to searching the PATH for an installation of the Python interpretor. This currently defaults to Python 2.7.x, which is normally installed in c:\python27 on Windows by default. Also tell people in the README.txt's for the Visual Studio builds
2014-02-21 10:00:29 +00:00
<PythonPath>c:\python27</PythonPath>
MSVC Projects: Use UNIX Line endings ...for all files except the README.txt and the .sln files, which have to have DOS/Windows line endings. This makes application of patches, when applicable, easier.
2013-12-04 00:51:39 +00:00
</PropertyGroup>
<PropertyGroup>
<_PropertySheetDisplayName>gtkversionpathsprops</_PropertySheetDisplayName>
</PropertyGroup>
<ItemGroup>
<BuildMacro Include="VSVer">
<Value>$(VSVer)</Value>
</BuildMacro>
<BuildMacro Include="GlibEtcInstallRoot">
<Value>$(GlibEtcInstallRoot)</Value>
</BuildMacro>
<BuildMacro Include="CopyDir">
<Value>$(CopyDir)</Value>
</BuildMacro>
<BuildMacro Include="ApiVersion">
<Value>$(ApiVersion)</Value>
</BuildMacro>
MSVC Build Files: Use Real GTK+ Version Make the Visual C++-related build files contain the actual GTK+ version, by generating them during the configure stage and dist'ing them in the release tarballs. This is especially important for builds of introspection files, as one may need to look at the release version of GTK+ in those files.
2014-08-07 15:11:34 +00:00
<BuildMacro Include="GtkVersion">
<Value>$(GtkVersion)</Value>
</BuildMacro>
MSVC Projects: Use UNIX Line endings ...for all files except the README.txt and the .sln files, which have to have DOS/Windows line endings. This makes application of patches, when applicable, easier.
2013-12-04 00:51:39 +00:00
<BuildMacro Include="GtkLibtoolCompatibleDllPrefix">
<Value>$(GtkLibtoolCompatibleDllPrefix)</Value>
</BuildMacro>
<BuildMacro Include="GtkLibtoolCompatibleDllSuffix">
<Value>$(GtkLibtoolCompatibleDllSuffix)</Value>
</BuildMacro>
<BuildMacro Include="GtkSeparateVSDllPrefix">
<Value>$(GtkSeparateVSDllPrefix)</Value>
</BuildMacro>
<BuildMacro Include="GtkSeparateVSDllSuffix">
<Value>$(GtkSeparateVSDllSuffix)</Value>
</BuildMacro>
<BuildMacro Include="GtkDllPrefix">
<Value>$(GtkDllPrefix)</Value>
</BuildMacro>
<BuildMacro Include="GtkDllSuffix">
<Value>$(GtkDllSuffix)</Value>
</BuildMacro>
Make Visual Studio Build Process A Bit Simpler Add some flexibility in the property sheets for one building GTK+ that it also searches for a settable installation path of Python, in addition to searching the PATH for an installation of the Python interpretor. This currently defaults to Python 2.7.x, which is normally installed in c:\python27 on Windows by default. Also tell people in the README.txt's for the Visual Studio builds
2014-02-21 10:00:29 +00:00
<BuildMacro Include="PythonPath">
<Value>$(PythonPath)</Value>
</BuildMacro>
MSVC Projects: Use UNIX Line endings ...for all files except the README.txt and the .sln files, which have to have DOS/Windows line endings. This makes application of patches, when applicable, easier.
2013-12-04 00:51:39 +00:00
</ItemGroup>
MSVC Builds: Clean up gtk-version-paths.*props Remove lines that are not really referred to.
2014-04-03 07:07:44 +00:00
</Project>
Reference in New Issue Copy Permalink