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

127 lines
6.6 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>
<ProjectConfiguration Include="Debug|x64">
<Configuration>Debug</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="Release|Win32">
<Configuration>Release</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="Release|x64">
<Configuration>Release</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
</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>{5AE8F5CE-9103-4951-AEDE-EA2F3B573BE8}</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>gdk4</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" />
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|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>StaticLibrary</ConfigurationType>
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
<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>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|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>StaticLibrary</ConfigurationType>
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
<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|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>StaticLibrary</ConfigurationType>
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
<CharacterSet>MultiByte</CharacterSet>
<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>
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|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>StaticLibrary</ConfigurationType>
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
<CharacterSet>MultiByte</CharacterSet>
<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>
<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: 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="gtk4-build-defines.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)'=='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: 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="gtk4-build-defines.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|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: 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="gtk4-build-defines.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|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: 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="gtk4-build-defines.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" />
<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>..\..\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;$(GdkDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>EditAndContinue</DebugInformationFormat>
</ClCompile>
</ItemDefinitionGroup>
<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>..\..\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>$(GdkDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
</ItemDefinitionGroup>
<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>..\..\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;$(GdkDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
</ItemDefinitionGroup>
<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>..\..\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>$(GdkDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
</ItemDefinitionGroup>
<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 "gdk-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="..\..\gdk\gdkkeynames.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>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
<ImportGroup Label="ExtensionTargets">
</ImportGroup>
</Project>
Reference in New Issue Copy Permalink