AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity
1eb8d2ad09
gtk2/win32/vs12/gtk-4.vcxprojin

384 lines
22 KiB
Plaintext
Raw Normal View History

Visual Studio builds: Clean up projects a bit Consolidate the .lib's that we need to link to for GDK and GTK+ into the property sheets, and also link to setupapi.lib as that is needed by the port to the new GdkMonitor API.
2016-05-09 07:35:26 +00:00
<?xml version="1.0" encoding="utf-8"?>
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
<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<ItemGroup Label="ProjectConfigurations">
<ProjectConfiguration Include="Debug|Win32">
<Configuration>Debug</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<ProjectConfiguration Include="Debug_Vulkan|Win32">
<Configuration>Debug_Vulkan</Configuration>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<Platform>Win32</Platform>
</ProjectConfiguration>
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
<ProjectConfiguration Include="Debug|x64">
<Configuration>Debug</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<ProjectConfiguration Include="Debug_Vulkan|x64">
<Configuration>Debug_Vulkan</Configuration>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<Platform>x64</Platform>
</ProjectConfiguration>
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
<ProjectConfiguration Include="Release|Win32">
<Configuration>Release</Configuration>
<Platform>Win32</Platform>
<WholeProgramOptimization>true</WholeProgramOptimization>
</ProjectConfiguration>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<ProjectConfiguration Include="Release_Vulkan|Win32">
<Configuration>Release_Vulkan</Configuration>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<Platform>Win32</Platform>
</ProjectConfiguration>
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
<ProjectConfiguration Include="Release|x64">
<Configuration>Release</Configuration>
<Platform>x64</Platform>
<WholeProgramOptimization>true</WholeProgramOptimization>
</ProjectConfiguration>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<ProjectConfiguration Include="Release_Vulkan|x64">
<Configuration>Release_Vulkan</Configuration>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<Platform>x64</Platform>
</ProjectConfiguration>
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>
<PropertyGroup Label="Globals">
MSVC Builds: Update Project GUIDs This updates the Visual Studio Project GUIDs so that they don't repeat with the GTK+-2.24.x ones, as the 3.x projects can be used with the 2.24.x in a all-in-one solution file (such as when one wants to use a complete GTK+2 and GTK+3 stack when porting Windows applications from GTK+2 to GTK+3), and each project in a solution file is expected to have an unique GUID.
2015-09-21 08:50:00 +00:00
<ProjectGuid>{95A4B53D-2773-4406-A2C1-8FD2840BBAD8}</ProjectGuid>
Visual Studio builds: Update from [gdk|gtk]-3 to [gdk|gtk]-4 This updates all the projects files to be be named appropriately as we move from GTK-3.x to 4.x, and updates the autotools files so that things are distributed and generated properly. Also remove deprecated/gtkstatusicon-quartz.c from gtk/Makefile.am, as that was causing 'make dist' to fail as that file has been removed. This fixes 'make dist' with the updated existing project files in proper order. Note that this does not include the new GSK, which will be added later, so the project files do not yet build the whole stack on Visual Studio at this point.
2016-10-19 10:39:36 +00:00
<RootNamespace>gtk4</RootNamespace>
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
<Keyword>Win32Proj</Keyword>
</PropertyGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" />
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<CharacterSet>MultiByte</CharacterSet>
<PlatformToolset>v120</PlatformToolset>
</PropertyGroup>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug_Vulkan|Win32'" Label="Configuration">
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<ConfigurationType>DynamicLibrary</ConfigurationType>
<CharacterSet>MultiByte</CharacterSet>
<PlatformToolset>v120</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<CharacterSet>MultiByte</CharacterSet>
<PlatformToolset>v120</PlatformToolset>
</PropertyGroup>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug_Vulkan|x64'" Label="Configuration">
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<ConfigurationType>DynamicLibrary</ConfigurationType>
<CharacterSet>MultiByte</CharacterSet>
<PlatformToolset>v120</PlatformToolset>
</PropertyGroup>
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 Condition="'$(Configuration)|$(Platform)'=='Release|Win32'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<CharacterSet>MultiByte</CharacterSet>
MSVC builds: Support MSVC 2013 and later We now need C99 features from the compiler which are only supported by Visual Studio 2013 and later, so drop the MSVC 2008~2012 projects, and make the baseline supported Visual Studio version be 2013. Update the build files as a result.
2016-10-26 05:42:43 +00:00
<PlatformToolset>v120</PlatformToolset>
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>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release_Vulkan|Win32'" Label="Configuration">
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
<ConfigurationType>DynamicLibrary</ConfigurationType>
<CharacterSet>MultiByte</CharacterSet>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<WholeProgramOptimization>true</WholeProgramOptimization>
MSVC builds: Support MSVC 2013 and later We now need C99 features from the compiler which are only supported by Visual Studio 2013 and later, so drop the MSVC 2008~2012 projects, and make the baseline supported Visual Studio version be 2013. Update the build files as a result.
2016-10-26 05:42:43 +00:00
<PlatformToolset>v120</PlatformToolset>
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 Condition="'$(Configuration)|$(Platform)'=='Release|x64'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<CharacterSet>MultiByte</CharacterSet>
MSVC builds: Support MSVC 2013 and later We now need C99 features from the compiler which are only supported by Visual Studio 2013 and later, so drop the MSVC 2008~2012 projects, and make the baseline supported Visual Studio version be 2013. Update the build files as a result.
2016-10-26 05:42:43 +00:00
<PlatformToolset>v120</PlatformToolset>
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>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release_Vulkan|x64'" Label="Configuration">
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
<ConfigurationType>DynamicLibrary</ConfigurationType>
<CharacterSet>MultiByte</CharacterSet>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<WholeProgramOptimization>true</WholeProgramOptimization>
MSVC builds: Support MSVC 2013 and later We now need C99 features from the compiler which are only supported by Visual Studio 2013 and later, so drop the MSVC 2008~2012 projects, and make the baseline supported Visual Studio version be 2013. Update the build files as a result.
2016-10-26 05:42:43 +00:00
<PlatformToolset>v120</PlatformToolset>
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>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.props" />
<ImportGroup Label="ExtensionSettings">
</ImportGroup>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<Import Project="gtk4-gen-srcs.props" />
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
</ImportGroup>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='Debug_Vulkan|Win32'" Label="PropertySheets">
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<Import Project="gtk4-gen-srcs.props" />
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<Import Project="gtk4-gen-srcs.props" />
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
</ImportGroup>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='Debug_Vulkan|x64'" Label="PropertySheets">
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<Import Project="gtk4-gen-srcs.props" />
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
</ImportGroup>
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
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<Import Project="gtk4-gen-srcs.props" />
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
</ImportGroup>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='Release_Vulkan|Win32'" Label="PropertySheets">
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
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<Import Project="gtk4-gen-srcs.props" />
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
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<Import Project="gtk4-gen-srcs.props" />
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
</ImportGroup>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='Release_Vulkan|x64'" Label="PropertySheets">
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
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<Import Project="gtk4-gen-srcs.props" />
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
</ImportGroup>
<PropertyGroup Label="UserMacros" />
<PropertyGroup>
Visual Studio builds: Clean up project files There are items in there that can be combined, as there are mostly no differences between x64 and Win32 configs for source/data file generation.
2016-12-30 04:46:55 +00:00
<LinkIncremental Condition="'$(Configuration)'=='Debug'">true</LinkIncremental>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<LinkIncremental Condition="'$(Configuration)'=='Debug_Vulkan'">true</LinkIncremental>
Visual Studio builds: Clean up project files There are items in there that can be combined, as there are mostly no differences between x64 and Win32 configs for source/data file generation.
2016-12-30 04:46:55 +00:00
<LinkIncremental Condition="'$(Configuration)'=='Release'">false</LinkIncremental>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<LinkIncremental Condition="'$(Configuration)'=='Release_Vulkan'">false</LinkIncremental>
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>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">
<ClCompile>
<Optimization>Disabled</Optimization>
Visual Studio builds: Move project files to win32/ It was suggested that the project files to be moved to win32/, so that we can have one less layer of directories we need to go down into to reach the project files.
2017-01-09 07:33:25 +00:00
<AdditionalIncludeDirectories>..\..\gtk;..\..\gdk;..\..\gdk\win32;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
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
<PreprocessorDefinitions>_DEBUG;G_ENABLE_DEBUG;$(GtkDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>EditAndContinue</DebugInformationFormat>
</ClCompile>
<Link>
Visual Studio builds: Clean up projects a bit Consolidate the .lib's that we need to link to for GDK and GTK+ into the property sheets, and also link to setupapi.lib as that is needed by the port to the new GdkMonitor API.
2016-05-09 07:35:26 +00:00
<AdditionalDependencies>$(GtkAdditionalLibs);%(AdditionalDependencies)</AdditionalDependencies>
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
<OutputFile>$(OutDir)$(GtkDllPrefix)$(ProjectName)$(GtkDllSuffix).dll</OutputFile>
Visual Studio builds: Use gtk-4.lib for the .lib file As with the autotools builds, use gtk-4 as the name of the .lib file that is produced from the build. Actually this is already done with GTK-3.x with the autotools builds, but this update is not done there as gtk-3.0.lib/gdk-3.0.lib/gailutil-3.0.lib was used for such a long time that changing it there might have caused trouble for people there.
2016-11-03 09:46:32 +00:00
<ImportLibrary>$(TargetDir)$(ProjectName).lib</ImportLibrary>
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
<GenerateDebugInformation>true</GenerateDebugInformation>
<ProgramDatabaseFile>$(OutDir)$(GtkDllPrefix)$(ProjectName)$(GtkDllSuffix).pdb</ProgramDatabaseFile>
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<AdditionalOptions>$(GtkExportGdkWin32DisplayMgr) %(AdditionalOptions)</AdditionalOptions>
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
<SubSystem>Windows</SubSystem>
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug_Vulkan|Win32'">
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<ClCompile>
<Optimization>Disabled</Optimization>
Visual Studio builds: Move project files to win32/ It was suggested that the project files to be moved to win32/, so that we can have one less layer of directories we need to go down into to reach the project files.
2017-01-09 07:33:25 +00:00
<AdditionalIncludeDirectories>..\..\gtk;..\..\gdk;..\..\gdk\win32;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<PreprocessorDefinitions>_DEBUG;G_ENABLE_DEBUG;$(GtkDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>EditAndContinue</DebugInformationFormat>
</ClCompile>
<Link>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<AdditionalDependencies>$(GtkAdditionalLibs);$(VulkanLibs);%(AdditionalDependencies)</AdditionalDependencies>
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<OutputFile>$(SolutionDir)Debug\$(Platform)\bin\$(GtkDllPrefix)$(ProjectName)$(GtkDllSuffix).dll</OutputFile>
<ImportLibrary>$(SolutionDir)Debug\$(Platform)\bin\$(ProjectName).lib</ImportLibrary>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<GenerateDebugInformation>true</GenerateDebugInformation>
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<ProgramDatabaseFile>$(SolutionDir)Debug\$(Platform)\bin\$(GtkDllPrefix)$(ProjectName)$(GtkDllSuffix).pdb</ProgramDatabaseFile>
<AdditionalOptions>$(GtkExportGdkWin32DisplayMgr) %(AdditionalOptions)</AdditionalOptions>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<SubSystem>Windows</SubSystem>
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
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
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">
<ClCompile>
Visual Studio builds: Move project files to win32/ It was suggested that the project files to be moved to win32/, so that we can have one less layer of directories we need to go down into to reach the project files.
2017-01-09 07:33:25 +00:00
<AdditionalIncludeDirectories>..\..\gtk;..\..\gdk;..\..\gdk\win32;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
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
<PreprocessorDefinitions>$(GtkDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<Link>
Visual Studio builds: Clean up projects a bit Consolidate the .lib's that we need to link to for GDK and GTK+ into the property sheets, and also link to setupapi.lib as that is needed by the port to the new GdkMonitor API.
2016-05-09 07:35:26 +00:00
<AdditionalDependencies>$(GtkAdditionalLibs);%(AdditionalDependencies)</AdditionalDependencies>
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
<OutputFile>$(OutDir)$(GtkDllPrefix)$(ProjectName)$(GtkDllSuffix).dll</OutputFile>
Visual Studio builds: Use gtk-4.lib for the .lib file As with the autotools builds, use gtk-4 as the name of the .lib file that is produced from the build. Actually this is already done with GTK-3.x with the autotools builds, but this update is not done there as gtk-3.0.lib/gdk-3.0.lib/gailutil-3.0.lib was used for such a long time that changing it there might have caused trouble for people there.
2016-11-03 09:46:32 +00:00
<ImportLibrary>$(TargetDir)$(ProjectName).lib</ImportLibrary>
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
<GenerateDebugInformation>true</GenerateDebugInformation>
<ProgramDatabaseFile>$(OutDir)$(GtkDllPrefix)$(ProjectName)$(GtkDllSuffix).pdb</ProgramDatabaseFile>
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<AdditionalOptions>$(GtkExportGdkWin32DisplayMgr) %(AdditionalOptions)</AdditionalOptions>
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
<SubSystem>Windows</SubSystem>
<OptimizeReferences>true</OptimizeReferences>
<EnableCOMDATFolding>true</EnableCOMDATFolding>
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release_Vulkan|Win32'">
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<ClCompile>
Visual Studio builds: Move project files to win32/ It was suggested that the project files to be moved to win32/, so that we can have one less layer of directories we need to go down into to reach the project files.
2017-01-09 07:33:25 +00:00
<AdditionalIncludeDirectories>..\..\gtk;..\..\gdk;..\..\gdk\win32;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<PreprocessorDefinitions>$(GtkDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<Link>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<AdditionalDependencies>$(GtkAdditionalLibs);$(VulkanLibs);%(AdditionalDependencies)</AdditionalDependencies>
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<OutputFile>$(SolutionDir)Release\$(Platform)\bin\$(GtkDllPrefix)$(ProjectName)$(GtkDllSuffix).dll</OutputFile>
<ImportLibrary>$(SolutionDir)Release\$(Platform)\bin\$(ProjectName).lib</ImportLibrary>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<GenerateDebugInformation>true</GenerateDebugInformation>
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<ProgramDatabaseFile>$(SolutionDir)Release\$(Platform)\bin\$(GtkDllPrefix)$(ProjectName)$(GtkDllSuffix).pdb</ProgramDatabaseFile>
<AdditionalOptions>$(GtkExportGdkWin32DisplayMgr) %(AdditionalOptions)</AdditionalOptions>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<SubSystem>Windows</SubSystem>
<OptimizeReferences>true</OptimizeReferences>
<EnableCOMDATFolding>true</EnableCOMDATFolding>
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
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
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">
<ClCompile>
<Optimization>Disabled</Optimization>
Visual Studio builds: Move project files to win32/ It was suggested that the project files to be moved to win32/, so that we can have one less layer of directories we need to go down into to reach the project files.
2017-01-09 07:33:25 +00:00
<AdditionalIncludeDirectories>..\..\gtk;..\..\gdk;..\..\gdk\win32;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
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
<PreprocessorDefinitions>_DEBUG;G_ENABLE_DEBUG;$(GtkDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<Link>
Visual Studio builds: Clean up projects a bit Consolidate the .lib's that we need to link to for GDK and GTK+ into the property sheets, and also link to setupapi.lib as that is needed by the port to the new GdkMonitor API.
2016-05-09 07:35:26 +00:00
<AdditionalDependencies>$(GtkAdditionalLibs);%(AdditionalDependencies)</AdditionalDependencies>
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
<OutputFile>$(OutDir)$(GtkDllPrefix)$(ProjectName)$(GtkDllSuffix).dll</OutputFile>
Visual Studio builds: Use gtk-4.lib for the .lib file As with the autotools builds, use gtk-4 as the name of the .lib file that is produced from the build. Actually this is already done with GTK-3.x with the autotools builds, but this update is not done there as gtk-3.0.lib/gdk-3.0.lib/gailutil-3.0.lib was used for such a long time that changing it there might have caused trouble for people there.
2016-11-03 09:46:32 +00:00
<ImportLibrary>$(TargetDir)$(ProjectName).lib</ImportLibrary>
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
<GenerateDebugInformation>true</GenerateDebugInformation>
<ProgramDatabaseFile>$(OutDir)$(GtkDllPrefix)$(ProjectName)$(GtkDllSuffix).pdb</ProgramDatabaseFile>
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<AdditionalOptions>$(GtkExportGdkWin32DisplayMgr) %(AdditionalOptions)</AdditionalOptions>
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
<SubSystem>Windows</SubSystem>
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug_Vulkan|x64'">
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<ClCompile>
<Optimization>Disabled</Optimization>
Visual Studio builds: Move project files to win32/ It was suggested that the project files to be moved to win32/, so that we can have one less layer of directories we need to go down into to reach the project files.
2017-01-09 07:33:25 +00:00
<AdditionalIncludeDirectories>..\..\gtk;..\..\gdk;..\..\gdk\win32;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<PreprocessorDefinitions>_DEBUG;G_ENABLE_DEBUG;$(GtkDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<Link>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<AdditionalDependencies>$(GtkAdditionalLibs);$(VulkanLibs);%(AdditionalDependencies)</AdditionalDependencies>
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<OutputFile>$(SolutionDir)Debug\$(Platform)\bin\$(GtkDllPrefix)$(ProjectName)$(GtkDllSuffix).dll</OutputFile>
<ImportLibrary>$(SolutionDir)Debug\$(Platform)\bin\$(ProjectName).lib</ImportLibrary>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<GenerateDebugInformation>true</GenerateDebugInformation>
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<ProgramDatabaseFile>$(SolutionDir)Debug\$(Platform)\bin\$(GtkDllPrefix)$(ProjectName)$(GtkDllSuffix).pdb</ProgramDatabaseFile>
<AdditionalOptions>$(GtkExportGdkWin32DisplayMgr) %(AdditionalOptions)</AdditionalOptions>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<SubSystem>Windows</SubSystem>
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
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
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'">
<ClCompile>
Visual Studio builds: Move project files to win32/ It was suggested that the project files to be moved to win32/, so that we can have one less layer of directories we need to go down into to reach the project files.
2017-01-09 07:33:25 +00:00
<AdditionalIncludeDirectories>..\..\gtk;..\..\gdk;..\..\gdk\win32;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
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
<PreprocessorDefinitions>$(GtkDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<Link>
Visual Studio builds: Clean up projects a bit Consolidate the .lib's that we need to link to for GDK and GTK+ into the property sheets, and also link to setupapi.lib as that is needed by the port to the new GdkMonitor API.
2016-05-09 07:35:26 +00:00
<AdditionalDependencies>$(GtkAdditionalLibs);%(AdditionalDependencies)</AdditionalDependencies>
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
<OutputFile>$(OutDir)$(GtkDllPrefix)$(ProjectName)$(GtkDllSuffix).dll</OutputFile>
Visual Studio builds: Use gtk-4.lib for the .lib file As with the autotools builds, use gtk-4 as the name of the .lib file that is produced from the build. Actually this is already done with GTK-3.x with the autotools builds, but this update is not done there as gtk-3.0.lib/gdk-3.0.lib/gailutil-3.0.lib was used for such a long time that changing it there might have caused trouble for people there.
2016-11-03 09:46:32 +00:00
<ImportLibrary>$(TargetDir)$(ProjectName).lib</ImportLibrary>
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
<GenerateDebugInformation>true</GenerateDebugInformation>
<ProgramDatabaseFile>$(OutDir)$(GtkDllPrefix)$(ProjectName)$(GtkDllSuffix).pdb</ProgramDatabaseFile>
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<AdditionalOptions>$(GtkExportGdkWin32DisplayMgr) %(AdditionalOptions)</AdditionalOptions>
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
<SubSystem>Windows</SubSystem>
<OptimizeReferences>true</OptimizeReferences>
<EnableCOMDATFolding>true</EnableCOMDATFolding>
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release_Vulkan|x64'">
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<ClCompile>
Visual Studio builds: Move project files to win32/ It was suggested that the project files to be moved to win32/, so that we can have one less layer of directories we need to go down into to reach the project files.
2017-01-09 07:33:25 +00:00
<AdditionalIncludeDirectories>..\..\gtk;..\..\gdk;..\..\gdk\win32;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<PreprocessorDefinitions>$(GtkDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<Link>
Visual Studio builds: Support Vulkan builds This will assume that the Vulkan SDK can be found in the INCLUDE/LIB paths that are used by the Visual Studio compiler.
2016-12-30 06:42:38 +00:00
<AdditionalDependencies>$(GtkAdditionalLibs);$(VulkanLibs);%(AdditionalDependencies)</AdditionalDependencies>
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<OutputFile>$(SolutionDir)Release\$(Platform)\bin\$(GtkDllPrefix)$(ProjectName)$(GtkDllSuffix).dll</OutputFile>
<ImportLibrary>$(SolutionDir)Release\$(Platform)\bin\$(ProjectName).lib</ImportLibrary>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<GenerateDebugInformation>true</GenerateDebugInformation>
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<ProgramDatabaseFile>$(SolutionDir)Release\$(Platform)\bin\$(GtkDllPrefix)$(ProjectName)$(GtkDllSuffix).pdb</ProgramDatabaseFile>
<AdditionalOptions>$(GtkExportGdkWin32DisplayMgr) %(AdditionalOptions)</AdditionalOptions>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<SubSystem>Windows</SubSystem>
<OptimizeReferences>true</OptimizeReferences>
<EnableCOMDATFolding>true</EnableCOMDATFolding>
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
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>
Visual Studio builds: Move project files to win32/ It was suggested that the project files to be moved to win32/, so that we can have one less layer of directories we need to go down into to reach the project files.
2017-01-09 07:33:25 +00:00
<CustomBuild Include="..\..\gtk\gtkdbusinterfaces.xml">
MSVC builds: Allow different Python versions per toolset Use conditionals to select the Python installation, so that we can stick closer to the default Visual Studio versions used to compile each official Python releases. This means by default: -2013 builds use Python 3.4.x, which is built with 2010 -2015 and 2017 builds use Python 3.6.x, which is built with 2015. Also rename PythonPath/PythonPathX64 in the property sheets to PythonDir/PythonDirX64 repsectively, as PythonPath is the envvar name where additional Python modules is searched for, so we don't want to get confused with it. Last but not least, distinguish between the Python interpretors that are used on x64 and x86/32-bit builds for generating the libgtk4.manifest file and the gdbus-generated sources, for consistency reasons.
2017-07-31 09:25:56 +00:00
<Message Condition="'$(Platform)'=='Win32'">Generating GTK+ DBus Sources...</Message>
<Command Condition="'$(Platform)'=='Win32'">$(GenerateGtkDbusBuiltSources)</Command>
<Outputs Condition="'$(Platform)'=='Win32'">..\..\gtk\gtkdbusgenerated.c;..\..\gtk\gtkdbusgenerated.h;%(Outputs)</Outputs>
<Message Condition="'$(Platform)'=='x64'">Generating GTK+ DBus Sources...</Message>
<Command Condition="'$(Platform)'=='x64'">$(GenerateGtkDbusBuiltSourcesX64)</Command>
<Outputs Condition="'$(Platform)'=='x64'">..\..\gtk\gtkdbusgenerated.c;..\..\gtk\gtkdbusgenerated.h;%(Outputs)</Outputs>
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
</CustomBuild>
Visual Studio builds: Move project files to win32/ It was suggested that the project files to be moved to win32/, so that we can have one less layer of directories we need to go down into to reach the project files.
2017-01-09 07:33:25 +00:00
<CustomBuild Include="..\..\gtk\gtk-win32.rc.body">
MSVC builds: Allow different Python versions per toolset Use conditionals to select the Python installation, so that we can stick closer to the default Visual Studio versions used to compile each official Python releases. This means by default: -2013 builds use Python 3.4.x, which is built with 2010 -2015 and 2017 builds use Python 3.6.x, which is built with 2015. Also rename PythonPath/PythonPathX64 in the property sheets to PythonDir/PythonDirX64 repsectively, as PythonPath is the envvar name where additional Python modules is searched for, so we don't want to get confused with it. Last but not least, distinguish between the Python interpretors that are used on x64 and x86/32-bit builds for generating the libgtk4.manifest file and the gdbus-generated sources, for consistency reasons.
2017-07-31 09:25:56 +00:00
<Message>Copying GTK+ Win32 Version Resource...</Message>
<Command>$(CopyGtkWin32RC)</Command>
<Outputs>..\..\gtk\gtk-win32.rc;%(Outputs)</Outputs>
Windows: Update how gtk-win32.rc is generated On Visual Studio, unlike MinGW, manifest files are embedded via including the manifest file as a resource file in the projects, not via the .rc file. This means that the line in the .rc file that specifies the manifest file would cause trouble, so that line gets removed when the full gtk3-win32.rc is generated on Visual Studio builds, otherwise 2010+ Visual Studio will complain when compiling the .rc file. Also, the inclusion of winuser.h will cause warnings during the compilation of the .rc file. Fix this by isolating the Win32 resource portions of gtk-win32.rc.in to gtk-win32.rc.body.in and: -On MinGW, construct the full gtk-win32.rc by doing the winver.h and winuser.h inclusion first, then append the contents of gtk-win32.rc.body, and then appending the line to embed the manifest file. -On Visual Studio, simply copy the gtk-win32.rc.body to gtk-win32.rc, and generate the full libgtk3.manifest file. https://bugzilla.gnome.org/show_bug.cgi?id=762311
2016-02-22 09:38:15 +00:00
</CustomBuild>
Visual Studio builds: Move project files to win32/ It was suggested that the project files to be moved to win32/, so that we can have one less layer of directories we need to go down into to reach the project files.
2017-01-09 07:33:25 +00:00
<CustomBuild Include="..\..\gtk\libgtk4.manifest.in">
MSVC builds: Allow different Python versions per toolset Use conditionals to select the Python installation, so that we can stick closer to the default Visual Studio versions used to compile each official Python releases. This means by default: -2013 builds use Python 3.4.x, which is built with 2010 -2015 and 2017 builds use Python 3.6.x, which is built with 2015. Also rename PythonPath/PythonPathX64 in the property sheets to PythonDir/PythonDirX64 repsectively, as PythonPath is the envvar name where additional Python modules is searched for, so we don't want to get confused with it. Last but not least, distinguish between the Python interpretors that are used on x64 and x86/32-bit builds for generating the libgtk4.manifest file and the gdbus-generated sources, for consistency reasons.
2017-07-31 09:25:56 +00:00
<Message Condition="'$(Platform)'=='Win32'">Generating GTK+ Win32 Manifest...</Message>
<Command Condition="'$(Platform)'=='Win32'">$(GenerateGtkWin32Manifest)</Command>
<Outputs Condition="'$(Platform)'=='Win32'">..\..\gtk\libgtk4.manifest;%(Outputs)</Outputs>
<Message Condition="'$(Platform)'=='x64'">Generating GTK+ Win32 Manifest...</Message>
<Command Condition="'$(Platform)'=='x64'">$(GenerateGtkWin32ManifestX64)</Command>
<Outputs Condition="'$(Platform)'=='x64'">..\..\gtk\libgtk4.manifest;%(Outputs)</Outputs>
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
</CustomBuild>
</ItemGroup>
<ItemGroup>
Visual Studio builds: Move project files to win32/ It was suggested that the project files to be moved to win32/, so that we can have one less layer of directories we need to go down into to reach the project files.
2017-01-09 07:33:25 +00:00
<ResourceCompile Include="..\..\gtk\gtk-win32.rc">
<AdditionalIncludeDirectories>..\..\gdk\win32\rc;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
</ResourceCompile>
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>
<ItemGroup>
MSVC builds: Support MSVC 2013 and later We now need C99 features from the compiler which are only supported by Visual Studio 2013 and later, so drop the MSVC 2008~2012 projects, and make the baseline supported Visual Studio version be 2013. Update the build files as a result.
2016-10-26 05:42:43 +00:00
#include "gtk-4.vs12.sourcefiles"
Visual Studio builds: Move project files to win32/ It was suggested that the project files to be moved to win32/, so that we can have one less layer of directories we need to go down into to reach the project files.
2017-01-09 07:33:25 +00:00
<ClCompile Include="..\..\modules\input\gtkimcontextime.c" />
<ClCompile Include="..\..\modules\input\gtkimcontextmultipress.c" />
<ClCompile Include="..\..\modules\input\gtkimcontextthai.c" />
<ClCompile Include="..\..\modules\input\imam-et.c" />
<ClCompile Include="..\..\modules\input\imcedilla.c" />
<ClCompile Include="..\..\modules\input\imcyrillic-translit.c" />
<ClCompile Include="..\..\modules\input\imime.c" />
<ClCompile Include="..\..\modules\input\iminuktitut.c" />
<ClCompile Include="..\..\modules\input\imipa.c" />
<ClCompile Include="..\..\modules\input\immultipress.c" />
<ClCompile Include="..\..\modules\input\imthai.c" />
<ClCompile Include="..\..\modules\input\imti-er.c" />
<ClCompile Include="..\..\modules\input\imti-et.c" />
<ClCompile Include="..\..\modules\input\imviqr.c" />
<ClCompile Include="..\..\modules\input\thai-charprop.c" />
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>
<ItemGroup>
Visual Studio builds: Move project files to win32/ It was suggested that the project files to be moved to win32/, so that we can have one less layer of directories we need to go down into to reach the project files.
2017-01-09 07:33:25 +00:00
<Manifest Include="..\..\gtk\libgtk4.manifest" />
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>
<ItemGroup>
Visual Studio builds: Build GTK+ as a monolithic DLL Update the project configs to build GDK/GSK as a static lib and include them into the GTK+ DLL as a monolithic DLL, which is in line with what is done in the autotools builds, since the code changes needed for Windows builds for a monolithic build are now in place.
2016-11-03 09:17:57 +00:00
<ProjectReference Include="gdk4-win32.vcxproj">
<Project>{aba7685a-7cbb-4626-b5e5-6eeea5b489ef}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
Visual Studio builds: Update from [gdk|gtk]-3 to [gdk|gtk]-4 This updates all the projects files to be be named appropriately as we move from GTK-3.x to 4.x, and updates the autotools files so that things are distributed and generated properly. Also remove deprecated/gtkstatusicon-quartz.c from gtk/Makefile.am, as that was causing 'make dist' to fail as that file has been removed. This fixes 'make dist' with the updated existing project files in proper order. Note that this does not include the new GSK, which will be added later, so the project files do not yet build the whole stack on Visual Studio at this point.
2016-10-19 10:39:36 +00:00
<ProjectReference Include="gdk-4.vcxproj">
MSVC Builds: Update Project GUIDs This updates the Visual Studio Project GUIDs so that they don't repeat with the GTK+-2.24.x ones, as the 3.x projects can be used with the 2.24.x in a all-in-one solution file (such as when one wants to use a complete GTK+2 and GTK+3 stack when porting Windows applications from GTK+2 to GTK+3), and each project in a solution file is expected to have an unique GUID.
2015-09-21 08:50:00 +00:00
<Project>{5ae8f5ce-9103-4951-aede-ea2f3b573be8}</Project>
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
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
GSK: Add initial Visual Studio projects This adds the initial MSVC build items needed to build GSK under Visual Studio, this is part of it that is required, we need to add items to the property sheets to generate the code that is generated via glib-mkenums and glib-compile-resources. This set includes, with the autotools scripts for the complete: -GSK project files, which is integrated into the gtk+-4.sln. -The NMake snippets to build the introspection files for GSK. -The .bat files to call glib-mkenums to generate the enumeration sources.
2016-10-26 10:23:38 +00:00
<ProjectReference Include="gsk-4.vcxproj">
<Project>{5ae8f5ce-9103-4951-aede-eb2f3b573be8}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
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>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
<ImportGroup Label="ExtensionTargets">
</ImportGroup>
</Project>
Reference in New Issue Copy Permalink