AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity
3aaae6c49c
gtk2/build/win32/vs9/gtk3-demo.vcprojin

175 lines
4.0 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="Windows-1252"?>
<VisualStudioProject
ProjectType="Visual C++"
Version="9.00"
Name="gtk3-demo"
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="{BDAE6DE2-6BCC-4107-94F0-DA12214A02DE}"
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
RootNamespace="gtk3demo"
Keyword="Win32Proj"
TargetFrameworkVersion="131072"
>
<Platforms>
<Platform
Name="Win32"
/>
<Platform
Name="x64"
/>
</Platforms>
<ToolFiles>
</ToolFiles>
<Configurations>
<Configuration
Name="Debug|Win32"
ConfigurationType="1"
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
InheritedPropertySheets=".\gtk3-build-defines.vsprops"
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
CharacterSet="2"
>
<Tool
Name="VCPreBuildEventTool"
/>
<Tool
Name="VCCLCompilerTool"
Optimization="0"
AdditionalIncludeDirectories="..\..\..\gdk;..\..\..\gtk"
PreprocessorDefinitions="_DEBUG;$(GtkPrefixDefine)"
MinimalRebuild="true"
BasicRuntimeChecks="3"
RuntimeLibrary="3"
UsePrecompiledHeader="0"
WarningLevel="3"
DebugInformationFormat="4"
CompileAs="1"
/>
<Tool
Name="VCLinkerTool"
AdditionalDependencies=""
LinkIncremental="1"
GenerateDebugInformation="true"
SubSystem="1"
RandomizedBaseAddress="1"
DataExecutionPrevention="0"
TargetMachine="1"
/>
</Configuration>
<Configuration
Name="Debug|x64"
ConfigurationType="1"
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
InheritedPropertySheets=".\gtk3-build-defines.vsprops"
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
CharacterSet="2"
>
<Tool
Name="VCPreBuildEventTool"
/>
<Tool
Name="VCCLCompilerTool"
Optimization="0"
AdditionalIncludeDirectories="..\..\..\gdk;..\..\..\gtk"
PreprocessorDefinitions="_DEBUG;$(GtkPrefixDefine)"
MinimalRebuild="true"
BasicRuntimeChecks="3"
RuntimeLibrary="3"
UsePrecompiledHeader="0"
WarningLevel="3"
DebugInformationFormat="3"
CompileAs="1"
/>
<Tool
Name="VCLinkerTool"
AdditionalDependencies=""
LinkIncremental="1"
GenerateDebugInformation="true"
SubSystem="1"
RandomizedBaseAddress="1"
DataExecutionPrevention="0"
TargetMachine="17"
/>
</Configuration>
<Configuration
Name="Release|Win32"
ConfigurationType="1"
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
InheritedPropertySheets=".\gtk3-build-defines.vsprops"
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
CharacterSet="2"
WholeProgramOptimization="1"
>
<Tool
Name="VCPreBuildEventTool"
/>
<Tool
Name="VCCLCompilerTool"
AdditionalIncludeDirectories="..\..\..\gdk;..\..\..\gtk"
PreprocessorDefinitions="$(GtkPrefixDefine)"
RuntimeLibrary="2"
UsePrecompiledHeader="0"
WarningLevel="3"
DebugInformationFormat="3"
CompileAs="1"
/>
<Tool
Name="VCLinkerTool"
AdditionalDependencies=""
LinkIncremental="1"
GenerateDebugInformation="true"
SubSystem="1"
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="2"
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="2"
RandomizedBaseAddress="1"
DataExecutionPrevention="0"
TargetMachine="1"
/>
</Configuration>
<Configuration
Name="Release|x64"
ConfigurationType="1"
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
InheritedPropertySheets=".\gtk3-build-defines.vsprops"
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
CharacterSet="2"
WholeProgramOptimization="1"
>
<Tool
Name="VCPreBuildEventTool"
/>
<Tool
Name="VCCLCompilerTool"
AdditionalIncludeDirectories="..\..\..\gdk;..\..\..\gtk"
PreprocessorDefinitions="$(GtkPrefixDefine)"
RuntimeLibrary="2"
UsePrecompiledHeader="0"
WarningLevel="3"
DebugInformationFormat="3"
CompileAs="1"
/>
<Tool
Name="VCLinkerTool"
AdditionalDependencies=""
LinkIncremental="1"
GenerateDebugInformation="true"
SubSystem="1"
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="2"
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="2"
RandomizedBaseAddress="1"
DataExecutionPrevention="0"
TargetMachine="17"
/>
</Configuration>
</Configurations>
<References>
</References>
<Files>
<Filter
Name="Source Files"
Filter="cpp;c;cc;cxx;def;odl;idl;hpj;bat;asm;asmx"
UniqueIdentifier="{4FC737F1-C7A5-4376-A066-2A32D752A2FF}"
>
#include "gtk3-demo.sourcefiles"
</Filter>
<Filter
Name="Header Files"
Filter="h;hpp;hxx;hm;inl;inc;xsd"
UniqueIdentifier="{93995380-89BD-4b04-88EB-625FBE52EBFB}"
>
</Filter>
</Files>
<Globals>
</Globals>
</VisualStudioProject>
Reference in New Issue Copy Permalink