AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity
f40c61fb40
gtk2/win32/vs12/gtk4-icon-browser.vcxprojin

172 lines
8.2 KiB
Plaintext
Raw Normal View History

build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
<?xml version="1.0" encoding="utf-8"?>
<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>{343333C4-D46C-4C97-A986-959CCA6F1DE0}</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>gtk4iconbrowser</RootNamespace>
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
<Keyword>Win32Proj</Keyword>
</PropertyGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" />
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'" Label="Configuration">
<ConfigurationType>Application</ConfigurationType>
<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>
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'" Label="Configuration">
<ConfigurationType>Application</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>
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'" Label="Configuration">
<ConfigurationType>Application</ConfigurationType>
<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>
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'" Label="Configuration">
<ConfigurationType>Application</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>
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
</PropertyGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.props" />
<ImportGroup Label="ExtensionSettings">
</ImportGroup>
<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: 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
<Import Project="gtk4-build-defines.props" />
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
</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: 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
<Import Project="gtk4-build-defines.props" />
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +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: 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
<Import Project="gtk4-build-defines.props" />
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +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: 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
<Import Project="gtk4-build-defines.props" />
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +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>
<LinkIncremental Condition="'$(Configuration)'=='Release'">false</LinkIncremental>
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +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>..\..\demos\icon-browser;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>EditAndContinue</DebugInformationFormat>
</ClCompile>
<Link>
<GenerateDebugInformation>true</GenerateDebugInformation>
<SubSystem>Console</SubSystem>
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">
<ClCompile>
<Optimization>MaxSpeed</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>..\..\demos\icon-browser;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
<IntrinsicFunctions>true</IntrinsicFunctions>
<PreprocessorDefinitions>%(PreprocessorDefinitions)</PreprocessorDefinitions>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>false</FunctionLevelLinking>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<Link>
<GenerateDebugInformation>true</GenerateDebugInformation>
<SubSystem>Console</SubSystem>
MSVC builds: Use /opt:ref for release builds glib-compile-resources have been updated to ensure that the symbols generated are referred to, so that they will not be optimized out by the linker in release builds. We can change from /opt:noref to /opt:ref, which should improve optimization a bit.
2015-11-12 10:16:33 +00:00
<OptimizeReferences>true</OptimizeReferences>
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
<EnableCOMDATFolding>true</EnableCOMDATFolding>
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<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>..\..\demos\icon-browser;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<Link>
<GenerateDebugInformation>true</GenerateDebugInformation>
<SubSystem>Console</SubSystem>
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</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>..\..\demos\icon-browser;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
<IntrinsicFunctions>true</IntrinsicFunctions>
<PreprocessorDefinitions>%(PreprocessorDefinitions)</PreprocessorDefinitions>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>false</FunctionLevelLinking>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<Link>
<GenerateDebugInformation>true</GenerateDebugInformation>
<SubSystem>Console</SubSystem>
MSVC builds: Use /opt:ref for release builds glib-compile-resources have been updated to ensure that the symbols generated are referred to, so that they will not be optimized out by the linker in release builds. We can change from /opt:noref to /opt:ref, which should improve optimization a bit.
2015-11-12 10:16:33 +00:00
<OptimizeReferences>true</OptimizeReferences>
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
<EnableCOMDATFolding>true</EnableCOMDATFolding>
<TargetMachine>MachineX64</TargetMachine>
</Link>
</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 "gtk4-icon-browser.vs12.sourcefiles"
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
</ItemGroup>
<ItemGroup>
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="gtk-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>{95a4b53d-2773-4406-a2c1-8fd2840bbad8}</Project>
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
</ItemGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
<ImportGroup Label="ExtensionTargets">
</ImportGroup>
</Project>
Reference in New Issue Copy Permalink