AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity
c05d21c9af
gtk2/win32/vs1x-props/gtk3-version-paths.props.in

84 lines
4.3 KiB
Plaintext
Raw Normal View History

MSVC Builds: Massive Rename of Projects We need to rename the projects so that when these projects are added into an all-in-one solution file that will build the GTK+ 2/3 stack, the names of the projects will not collide with the GTK+-2.x ones, especially as GTK+-2.x and GTK+-3.x are done to co-exist on the same system. This is due to the case that the MSVC projects are directly carried over from the GTK+-2.x ones and was then updated for 3.x. We still need to update the GUIDs of the projects, so that they won't conflict with the GTK+-2.x ones.
2015-08-25 09:41:55 +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">
Visual Studio projects: Make property sheets shared ...for Visual Studio 2010 and later, since we used to copy them and merely update the value of $(VSVer) during 'make dist' as needed. Instead of doing that, move the property sheets for Visual Studio 2010, which is the base version that we use, into a directory of its own, and make the Visual Studio 2010~2022 projects look for them in that directory, and set VSVer according to the toolset version identified by each of the project files. The ARM64-specific property sheet needed for VS2017 and the VS2008 property sheets will remain as they are.
2022-05-17 04:33:22 +00:00
<VSVer Condition="'$(VisualStudioVersion)' == ''">10</VSVer>
<VSVer Condition="'$(VisualStudioVersion)' == '10.0'">10</VSVer>
<VSVer Condition="'$(VisualStudioVersion)' == '11.0'">11</VSVer>
<VSVer Condition="'$(VisualStudioVersion)' == '12.0'">12</VSVer>
<VSVer Condition="'$(VisualStudioVersion)' == '14.0'">14</VSVer>
<VSVer Condition="'$(VisualStudioVersion)' == '15.0'">15</VSVer>
<VSVer Condition="'$(VisualStudioVersion)' == '16.0'">16</VSVer>
<VSVer Condition="'$(VisualStudioVersion)' == '17.0'">17</VSVer>
Visual Studio projects: move projects to win32/ This will simplify our source tree a bit
2020-07-16 09:11:19 +00:00
<GlibEtcInstallRoot>$(SolutionDir)\..\..\..\vs$(VSVer)\$(Platform)</GlibEtcInstallRoot>
<CopyDir>..\..\..\vs$(VSVer)\$(Platform)</CopyDir>
MSVC Builds: Massive Rename of Projects We need to rename the projects so that when these projects are added into an all-in-one solution file that will build the GTK+ 2/3 stack, the names of the projects will not collide with the GTK+-2.x ones, especially as GTK+-2.x and GTK+-3.x are done to co-exist on the same system. This is due to the case that the MSVC projects are directly carried over from the GTK+-2.x ones and was then updated for 3.x. We still need to update the GUIDs of the projects, so that they won't conflict with the GTK+-2.x ones.
2015-08-25 09:41:55 +00:00
<ApiVersion>3.0</ApiVersion>
<GtkVersion>@GTK_VERSION@</GtkVersion>
<GtkLibtoolCompatibleDllPrefix>lib</GtkLibtoolCompatibleDllPrefix>
<GtkLibtoolCompatibleDllSuffix>.0-0</GtkLibtoolCompatibleDllSuffix>
<GtkSeparateVSDllPrefix />
<GtkSeparateVSDllSuffix>-vs$(VSVer)</GtkSeparateVSDllSuffix>
<GtkDllPrefix>$(GtkSeparateVSDllPrefix)</GtkDllPrefix>
<GtkDllSuffix>$(GtkSeparateVSDllSuffix)</GtkDllSuffix>
Visual Studio 201x builds: Clean up project files Combine repetitive parts, and unify using $(PythonDir) for all builds, which the paths set in the property sheets are now based on the Visual Studio version and platform combination.
2018-05-12 02:52:47 +00:00
<PythonDir Condition="'$(VisualStudioVersion)|$(Platform)' == '10.0|Win32'">c:\python34</PythonDir>
<PythonDir Condition="'$(VisualStudioVersion)|$(Platform)' == '11.0|Win32'">c:\python34</PythonDir>
<PythonDir Condition="'$(VisualStudioVersion)|$(Platform)' == '12.0|Win32'">c:\python34</PythonDir>
<PythonDir Condition="'$(VisualStudioVersion)|$(Platform)' == '14.0|Win32'">c:\python36</PythonDir>
<PythonDir Condition="'$(VisualStudioVersion)|$(Platform)' == '15.0|Win32'">c:\python36</PythonDir>
MSVC projects: Define a default PythonDir for VS2019 builds We still use Python 3.6.x for VS2019 builds as VS2015/2017 builds are binary compatible with 2019 builds.
2019-07-16 08:55:58 +00:00
<PythonDir Condition="'$(VisualStudioVersion)|$(Platform)' == '16.0|Win32'">c:\python36</PythonDir>
Visual Studio projects: "Add" Visual Studio 2022 projects Like the Visual Studio 2012+ projects, copy the Visual Studio 2010 projects and replace the items in there as needed, so that we can obtain Visual Studio 2022 project files, since they are all in the MSBuild format.
2021-10-14 02:44:25 +00:00
<PythonDir Condition="'$(VisualStudioVersion)|$(Platform)' == '17.0|Win32'">c:\python36</PythonDir>
Visual Studio 201x builds: Clean up project files Combine repetitive parts, and unify using $(PythonDir) for all builds, which the paths set in the property sheets are now based on the Visual Studio version and platform combination.
2018-05-12 02:52:47 +00:00
<PythonDir Condition="'$(VisualStudioVersion)|$(Platform)' == '10.0|x64'">c:\python34.x64</PythonDir>
<PythonDir Condition="'$(VisualStudioVersion)|$(Platform)' == '11.0|x64'">c:\python34.x64</PythonDir>
<PythonDir Condition="'$(VisualStudioVersion)|$(Platform)' == '12.0|x64'">c:\python34.x64</PythonDir>
<PythonDir Condition="'$(VisualStudioVersion)|$(Platform)' == '14.0|x64'">c:\python36.x64</PythonDir>
<PythonDir Condition="'$(VisualStudioVersion)|$(Platform)' == '15.0|x64'">c:\python36.x64</PythonDir>
MSVC projects: Define a default PythonDir for VS2019 builds We still use Python 3.6.x for VS2019 builds as VS2015/2017 builds are binary compatible with 2019 builds.
2019-07-16 08:55:58 +00:00
<PythonDir Condition="'$(VisualStudioVersion)|$(Platform)' == '16.0|x64'">c:\python36.x64</PythonDir>
Visual Studio projects: "Add" Visual Studio 2022 projects Like the Visual Studio 2012+ projects, copy the Visual Studio 2010 projects and replace the items in there as needed, so that we can obtain Visual Studio 2022 project files, since they are all in the MSBuild format.
2021-10-14 02:44:25 +00:00
<PythonDir Condition="'$(VisualStudioVersion)|$(Platform)' == '17.0|x64'">c:\python36.x64</PythonDir>
build: Integrate introspection builds into MSVC projects This is so that it is easier for one building GTK+ with Visual Studio to build the introspection files as well in one shot. Note that this is not built by default, so one needs to select the gtk3-introspect explicitly to build (and clean up) the introspection files. For this to work, one needs to ensure the following: -A complete build of GObject-Introspection in $(GlibEtcInstallRoot), that is built with the same installation of the Python interpretor that is used here (see PythonDir and PythonDirX64 in gtk3-version-paths.[vsprops|props]). -Introspection files for ATK, GDK-Pixbuf and Pango, also in their proper locations under $(GlibEtcInstallRoot), which should be built with the same G-I installation.
2017-08-28 08:18:24 +00:00
<IntrospectPythonParam>PYTHON=$(PythonDir)\python.exe</IntrospectPythonParam>
MSVC Builds: Massive Rename of Projects We need to rename the projects so that when these projects are added into an all-in-one solution file that will build the GTK+ 2/3 stack, the names of the projects will not collide with the GTK+-2.x ones, especially as GTK+-2.x and GTK+-3.x are done to co-exist on the same system. This is due to the case that the MSVC projects are directly carried over from the GTK+-2.x ones and was then updated for 3.x. We still need to update the GUIDs of the projects, so that they won't conflict with the GTK+-2.x ones.
2015-08-25 09:41:55 +00:00
</PropertyGroup>
<PropertyGroup>
<_PropertySheetDisplayName>gtk3versionpathsprops</_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>
<BuildMacro Include="GtkVersion">
<Value>$(GtkVersion)</Value>
</BuildMacro>
<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>
build: Use PythonDir in Visual Studio projects This is to avoid any confusion with the PYTHONPATH envvar that is used by Python for additional locations for looking for modules.
2017-08-28 06:58:42 +00:00
<BuildMacro Include="PythonDir">
<Value>$(PythonDir)</Value>
MSVC Builds: Massive Rename of Projects We need to rename the projects so that when these projects are added into an all-in-one solution file that will build the GTK+ 2/3 stack, the names of the projects will not collide with the GTK+-2.x ones, especially as GTK+-2.x and GTK+-3.x are done to co-exist on the same system. This is due to the case that the MSVC projects are directly carried over from the GTK+-2.x ones and was then updated for 3.x. We still need to update the GUIDs of the projects, so that they won't conflict with the GTK+-2.x ones.
2015-08-25 09:41:55 +00:00
</BuildMacro>
build: Integrate introspection builds into MSVC projects This is so that it is easier for one building GTK+ with Visual Studio to build the introspection files as well in one shot. Note that this is not built by default, so one needs to select the gtk3-introspect explicitly to build (and clean up) the introspection files. For this to work, one needs to ensure the following: -A complete build of GObject-Introspection in $(GlibEtcInstallRoot), that is built with the same installation of the Python interpretor that is used here (see PythonDir and PythonDirX64 in gtk3-version-paths.[vsprops|props]). -Introspection files for ATK, GDK-Pixbuf and Pango, also in their proper locations under $(GlibEtcInstallRoot), which should be built with the same G-I installation.
2017-08-28 08:18:24 +00:00
<BuildMacro Include="IntrospectPythonParam">
<Value>$(IntrospectPythonParam)</Value>
</BuildMacro>
MSVC Builds: Massive Rename of Projects We need to rename the projects so that when these projects are added into an all-in-one solution file that will build the GTK+ 2/3 stack, the names of the projects will not collide with the GTK+-2.x ones, especially as GTK+-2.x and GTK+-3.x are done to co-exist on the same system. This is due to the case that the MSVC projects are directly carried over from the GTK+-2.x ones and was then updated for 3.x. We still need to update the GUIDs of the projects, so that they won't conflict with the GTK+-2.x ones.
2015-08-25 09:41:55 +00:00
</ItemGroup>
</Project>
Reference in New Issue Copy Permalink