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

254 lines
19 KiB
Plaintext
Raw Normal View History

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
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 2013
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
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "gtk4-prebuild", "gtk4-prebuild.vcxproj", "{B98FBE68-B03C-48E3-8F32-C3C010720D30}"
Rework the Visual Studio 2010 Projects a bit Add a utility project to get config.h and gdkconfig.h from their *.h.win32 (or win32_broadway, if applicable) counterparts, using custom build rules, so that these "generated" files can also be removed on clean and "regenerated" upon update. This also enables the removal of configs in certain projects that isn't really needed as a result. Also update and merge the projects and property sheets to include a single property sheet that it needs, which will then in turn include the other property sheets that is needed, so that things are cleaner.
2013-12-30 05:17:43 +00:00
EndProject
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
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "gdk4-win32", "gdk4-win32.vcxproj", "{ABA7685A-7CBB-4626-B5E5-6EEEA5B489EF}"
Re-attempt to correct EOL on VS2010 solution This time I realized that I needed to set autocrlf=false on my Windows side ... ugh... This is one of those files that must have CRLF line endings to work correctly :|
2011-06-29 04:49:14 +00:00
EndProject
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
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "gdk-4", "gdk-4.vcxproj", "{5AE8F5CE-9103-4951-AEDE-EA2F3B573BE8}"
Re-attempt to correct EOL on VS2010 solution This time I realized that I needed to set autocrlf=false on my Windows side ... ugh... This is one of those files that must have CRLF line endings to work correctly :|
2011-06-29 04:49:14 +00:00
EndProject
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
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "gsk-4", "gsk-4.vcxproj", "{5AE8F5CE-9103-4951-AEDE-EB2F3B573BE8}"
EndProject
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
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "gtk-4", "gtk-4.vcxproj", "{95A4B53D-2773-4406-A2C1-8FD2840BBAD8}"
Re-attempt to correct EOL on VS2010 solution This time I realized that I needed to set autocrlf=false on my Windows side ... ugh... This is one of those files that must have CRLF line endings to work correctly :|
2011-06-29 04:49:14 +00:00
EndProject
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
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "gtk4-demo", "gtk4-demo.vcxproj", "{BDAE6DE2-6BCC-4107-94F0-DA12214A02DE}"
Re-attempt to correct EOL on VS2010 solution This time I realized that I needed to set autocrlf=false on my Windows side ... ugh... This is one of those files that must have CRLF line endings to work correctly :|
2011-06-29 04:49:14 +00:00
EndProject
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
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "gtk4-demo-application", "gtk4-demo-application.vcxproj", "{BE6B4973-C6FF-4C8F-8E97-A47793C50F44}"
Add Visual Studio project for gtk3-demo-application This is used by the "Application Class" demo... so this should be built as well especially as we are getting gspawn-win{32|64}-helper.exe fixed on Visual Studio 2005 (and later) builds.
2013-02-22 05:09:50 +00:00
EndProject
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
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "gtk4-icon-browser", "gtk4-icon-browser.vcxproj", "{343333C4-D46C-4C97-A986-959CCA6F1DE0}"
MSVC Builds: Build and Install gtk3-icon-browser Add the icon browser demo to the Visual Studio projects, and "install" it as well.
2014-09-23 10:54:34 +00:00
EndProject
MSVC builds: Fix previous patch on .sln file We need to change the filenames of the .vcxproj project files as well, oops.
2016-10-27 06:11:14 +00:00
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "gtk4-encode-symbolic-svg", "gtk4-encode-symbolic-svg.vcxproj", "{F280BF1A-777A-4FB5-8005-DFBE04621EDB}"
MSVC Builds: Build gtk-encode-symbolic-svg This utility would likely be useful for Windows builds of GTK+, given the reasons Alex cited for coming up with this utility[1], and MSVC build support for librsvg is not available at this time (possible, but not implemented yet). [1]: https://bugzilla.gnome.org/show_bug.cgi?id=730450
2014-08-04 07:07:39 +00:00
EndProject
MSVC builds: Fix previous patch on .sln file We need to change the filenames of the .vcxproj project files as well, oops.
2016-10-27 06:11:14 +00:00
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "gtk4-update-icon-cache", "gtk4-update-icon-cache.vcxproj", "{FC98AF16-4C68-42DF-906B-93A6804C198A}"
MSVC builds: Build more tools in gtk/ Build the gtk-update-icon-cache, gtk-builder-tool and gtk-query-settings tools and run gtk-update-icon-cache as part of the post-build "installation" process. Pointed out (and reminded) by Paolo Borelli in bug 759436 that we should build, "install" and run gtk-update-icon-cache in the MSVC builds as well.
2015-12-15 07:37:33 +00:00
EndProject
MSVC builds: Fix previous patch on .sln file We need to change the filenames of the .vcxproj project files as well, oops.
2016-10-27 06:11:14 +00:00
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "gtk4-builder-tool", "gtk4-builder-tool.vcxproj", "{7D2397CF-4C25-45BC-A1BB-CB4B6E154BBD}"
MSVC builds: Build more tools in gtk/ Build the gtk-update-icon-cache, gtk-builder-tool and gtk-query-settings tools and run gtk-update-icon-cache as part of the post-build "installation" process. Pointed out (and reminded) by Paolo Borelli in bug 759436 that we should build, "install" and run gtk-update-icon-cache in the MSVC builds as well.
2015-12-15 07:37:33 +00:00
EndProject
MSVC builds: Fix previous patch on .sln file We need to change the filenames of the .vcxproj project files as well, oops.
2016-10-27 06:11:14 +00:00
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "gtk4-query-settings", "gtk4-query-settings.vcxproj", "{9F22107A-3EF7-4B52-B269-747B65307F36}"
MSVC builds: Build more tools in gtk/ Build the gtk-update-icon-cache, gtk-builder-tool and gtk-query-settings tools and run gtk-update-icon-cache as part of the post-build "installation" process. Pointed out (and reminded) by Paolo Borelli in bug 759436 that we should build, "install" and run gtk-update-icon-cache in the MSVC builds as well.
2015-12-15 07:37:33 +00:00
EndProject
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
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "gtk4-install", "gtk4-install.vcxproj", "{23BBF35F-78AF-4E8C-983F-7B90448CD7DF}"
Re-attempt to correct EOL on VS2010 solution This time I realized that I needed to set autocrlf=false on my Windows side ... ugh... This is one of those files that must have CRLF line endings to work correctly :|
2011-06-29 04:49:14 +00:00
EndProject
Global
GlobalSection(SolutionConfigurationPlatforms) = preSolution
Debug|Win32 = Debug|Win32
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
Debug_Vulkan|Win32 = Debug_Vulkan|Win32
Re-attempt to correct EOL on VS2010 solution This time I realized that I needed to set autocrlf=false on my Windows side ... ugh... This is one of those files that must have CRLF line endings to work correctly :|
2011-06-29 04:49:14 +00:00
Debug|x64 = Debug|x64
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
Debug_Vulkan|x64 = Debug_Vulkan|x64
Re-attempt to correct EOL on VS2010 solution This time I realized that I needed to set autocrlf=false on my Windows side ... ugh... This is one of those files that must have CRLF line endings to work correctly :|
2011-06-29 04:49:14 +00:00
Release|Win32 = Release|Win32
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
Release_Vulkan|Win32 = Release_Vulkan|Win32
Re-attempt to correct EOL on VS2010 solution This time I realized that I needed to set autocrlf=false on my Windows side ... ugh... This is one of those files that must have CRLF line endings to work correctly :|
2011-06-29 04:49:14 +00:00
Release|x64 = Release|x64
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
Release_Vulkan|x64 = Release_Vulkan|x64
Re-attempt to correct EOL on VS2010 solution This time I realized that I needed to set autocrlf=false on my Windows side ... ugh... This is one of those files that must have CRLF line endings to work correctly :|
2011-06-29 04:49:14 +00:00
EndGlobalSection
GlobalSection(ProjectConfigurationPlatforms) = postSolution
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
{B98FBE68-B03C-48E3-8F32-C3C010720D30}.Debug|Win32.ActiveCfg = Debug|Win32
{B98FBE68-B03C-48E3-8F32-C3C010720D30}.Debug|Win32.Build.0 = Debug|Win32
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
{B98FBE68-B03C-48E3-8F32-C3C010720D30}.Debug_Vulkan|Win32.ActiveCfg = Debug_Vulkan|Win32
{B98FBE68-B03C-48E3-8F32-C3C010720D30}.Debug_Vulkan|Win32.Build.0 = Debug_Vulkan|Win32
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
{B98FBE68-B03C-48E3-8F32-C3C010720D30}.Debug|x64.ActiveCfg = Debug|x64
{B98FBE68-B03C-48E3-8F32-C3C010720D30}.Debug|x64.Build.0 = Debug|x64
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
{B98FBE68-B03C-48E3-8F32-C3C010720D30}.Debug_Vulkan|x64.ActiveCfg = Debug_Vulkan|x64
{B98FBE68-B03C-48E3-8F32-C3C010720D30}.Debug_Vulkan|x64.Build.0 = Debug_Vulkan|x64
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
{B98FBE68-B03C-48E3-8F32-C3C010720D30}.Release|Win32.ActiveCfg = Release|Win32
{B98FBE68-B03C-48E3-8F32-C3C010720D30}.Release|Win32.Build.0 = Release|Win32
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
{B98FBE68-B03C-48E3-8F32-C3C010720D30}.Release_Vulkan|Win32.ActiveCfg = Release_Vulkan|Win32
{B98FBE68-B03C-48E3-8F32-C3C010720D30}.Release_Vulkan|Win32.Build.0 = Release_Vulkan|Win32
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
{B98FBE68-B03C-48E3-8F32-C3C010720D30}.Release|x64.ActiveCfg = Release|x64
{B98FBE68-B03C-48E3-8F32-C3C010720D30}.Release|x64.Build.0 = Release|x64
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
{B98FBE68-B03C-48E3-8F32-C3C010720D30}.Release_Vulkan|x64.Build.0 = Release_Vulkan|x64
{B98FBE68-B03C-48E3-8F32-C3C010720D30}.Release_Vulkan|x64.ActiveCfg = Release_Vulkan|x64
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
{ABA7685A-7CBB-4626-B5E5-6EEEA5B489EF}.Debug|Win32.ActiveCfg = Debug|Win32
{ABA7685A-7CBB-4626-B5E5-6EEEA5B489EF}.Debug|Win32.Build.0 = Debug|Win32
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
{ABA7685A-7CBB-4626-B5E5-6EEEA5B489EF}.Debug_Vulkan|Win32.ActiveCfg = Debug|Win32
{ABA7685A-7CBB-4626-B5E5-6EEEA5B489EF}.Debug_Vulkan|Win32.Build.0 = Debug|Win32
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
{ABA7685A-7CBB-4626-B5E5-6EEEA5B489EF}.Debug|x64.ActiveCfg = Debug|x64
{ABA7685A-7CBB-4626-B5E5-6EEEA5B489EF}.Debug|x64.Build.0 = Debug|x64
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
{ABA7685A-7CBB-4626-B5E5-6EEEA5B489EF}.Debug_Vulkan|x64.ActiveCfg = Debug|x64
{ABA7685A-7CBB-4626-B5E5-6EEEA5B489EF}.Debug_Vulkan|x64.Build.0 = Debug|x64
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
{ABA7685A-7CBB-4626-B5E5-6EEEA5B489EF}.Release|Win32.ActiveCfg = Release|Win32
{ABA7685A-7CBB-4626-B5E5-6EEEA5B489EF}.Release|Win32.Build.0 = Release|Win32
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
{ABA7685A-7CBB-4626-B5E5-6EEEA5B489EF}.Release_Vulkan|Win32.ActiveCfg = Release|Win32
{ABA7685A-7CBB-4626-B5E5-6EEEA5B489EF}.Release_Vulkan|Win32.Build.0 = Release|Win32
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
{ABA7685A-7CBB-4626-B5E5-6EEEA5B489EF}.Release|x64.ActiveCfg = Release|x64
{ABA7685A-7CBB-4626-B5E5-6EEEA5B489EF}.Release|x64.Build.0 = Release|x64
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
{ABA7685A-7CBB-4626-B5E5-6EEEA5B489EF}.Release_Vulkan|x64.ActiveCfg = Release|x64
{ABA7685A-7CBB-4626-B5E5-6EEEA5B489EF}.Release_Vulkan|x64.Build.0 = Release|x64
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
{5AE8F5CE-9103-4951-AEDE-EA2F3B573BE8}.Debug|Win32.ActiveCfg = Debug|Win32
{5AE8F5CE-9103-4951-AEDE-EA2F3B573BE8}.Debug|Win32.Build.0 = Debug|Win32
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
{5AE8F5CE-9103-4951-AEDE-EA2F3B573BE8}.Debug_Vulkan|Win32.ActiveCfg = Debug|Win32
{5AE8F5CE-9103-4951-AEDE-EA2F3B573BE8}.Debug_Vulkan|Win32.Build.0 = Debug|Win32
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
{5AE8F5CE-9103-4951-AEDE-EA2F3B573BE8}.Debug|x64.ActiveCfg = Debug|x64
{5AE8F5CE-9103-4951-AEDE-EA2F3B573BE8}.Debug|x64.Build.0 = Debug|x64
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
{5AE8F5CE-9103-4951-AEDE-EA2F3B573BE8}.Debug_Vulkan|x64.ActiveCfg = Debug|x64
{5AE8F5CE-9103-4951-AEDE-EA2F3B573BE8}.Debug_Vulkan|x64.Build.0 = Debug|x64
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
{5AE8F5CE-9103-4951-AEDE-EA2F3B573BE8}.Release|Win32.ActiveCfg = Release|Win32
{5AE8F5CE-9103-4951-AEDE-EA2F3B573BE8}.Release|Win32.Build.0 = Release|Win32
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
{5AE8F5CE-9103-4951-AEDE-EA2F3B573BE8}.Release_Vulkan|Win32.ActiveCfg = Release|Win32
{5AE8F5CE-9103-4951-AEDE-EA2F3B573BE8}.Release_Vulkan|Win32.Build.0 = Release|Win32
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
{5AE8F5CE-9103-4951-AEDE-EA2F3B573BE8}.Release|x64.ActiveCfg = Release|x64
{5AE8F5CE-9103-4951-AEDE-EA2F3B573BE8}.Release|x64.Build.0 = Release|x64
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
{5AE8F5CE-9103-4951-AEDE-EA2F3B573BE8}.Release_Vulkan|x64.ActiveCfg = Release|x64
{5AE8F5CE-9103-4951-AEDE-EA2F3B573BE8}.Release_Vulkan|x64.Build.0 = Release|x64
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
{5AE8F5CE-9103-4951-AEDE-EB2F3B573BE8}.Debug|Win32.ActiveCfg = Debug|Win32
{5AE8F5CE-9103-4951-AEDE-EB2F3B573BE8}.Debug|Win32.Build.0 = Debug|Win32
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
{5AE8F5CE-9103-4951-AEDE-EB2F3B573BE8}.Debug_Vulkan|Win32.ActiveCfg = Debug_Vulkan|Win32
{5AE8F5CE-9103-4951-AEDE-EB2F3B573BE8}.Debug_Vulkan|Win32.Build.0 = Debug_Vulkan|Win32
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
{5AE8F5CE-9103-4951-AEDE-EB2F3B573BE8}.Debug|x64.ActiveCfg = Debug|x64
{5AE8F5CE-9103-4951-AEDE-EB2F3B573BE8}.Debug|x64.Build.0 = Debug|x64
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
{5AE8F5CE-9103-4951-AEDE-EB2F3B573BE8}.Debug_Vulkan|x64.ActiveCfg = Debug_Vulkan|x64
{5AE8F5CE-9103-4951-AEDE-EB2F3B573BE8}.Debug_Vulkan|x64.Build.0 = Debug_Vulkan|x64
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
{5AE8F5CE-9103-4951-AEDE-EB2F3B573BE8}.Release|Win32.ActiveCfg = Release|Win32
{5AE8F5CE-9103-4951-AEDE-EB2F3B573BE8}.Release|Win32.Build.0 = Release|Win32
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
{5AE8F5CE-9103-4951-AEDE-EB2F3B573BE8}.Release_Vulkan|Win32.ActiveCfg = Release_Vulkan|Win32
{5AE8F5CE-9103-4951-AEDE-EB2F3B573BE8}.Release_Vulkan|Win32.Build.0 = Release_Vulkan|Win32
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
{5AE8F5CE-9103-4951-AEDE-EB2F3B573BE8}.Release|x64.ActiveCfg = Release|x64
{5AE8F5CE-9103-4951-AEDE-EB2F3B573BE8}.Release|x64.Build.0 = Release|x64
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
{5AE8F5CE-9103-4951-AEDE-EB2F3B573BE8}.Release_Vulkan|x64.ActiveCfg = Release_Vulkan|x64
{5AE8F5CE-9103-4951-AEDE-EB2F3B573BE8}.Release_Vulkan|x64.Build.0 = Release_Vulkan|x64
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
{95A4B53D-2773-4406-A2C1-8FD2840BBAD8}.Debug|Win32.ActiveCfg = Debug|Win32
{95A4B53D-2773-4406-A2C1-8FD2840BBAD8}.Debug|Win32.Build.0 = Debug|Win32
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
{95A4B53D-2773-4406-A2C1-8FD2840BBAD8}.Debug_Vulkan|Win32.ActiveCfg = Debug_Vulkan|Win32
{95A4B53D-2773-4406-A2C1-8FD2840BBAD8}.Debug_Vulkan|Win32.Build.0 = Debug_Vulkan|Win32
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
{95A4B53D-2773-4406-A2C1-8FD2840BBAD8}.Debug|x64.ActiveCfg = Debug|x64
{95A4B53D-2773-4406-A2C1-8FD2840BBAD8}.Debug|x64.Build.0 = Debug|x64
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
{95A4B53D-2773-4406-A2C1-8FD2840BBAD8}.Debug_Vulkan|x64.ActiveCfg = Debug_Vulkan|x64
{95A4B53D-2773-4406-A2C1-8FD2840BBAD8}.Debug_Vulkan|x64.Build.0 = Debug_Vulkan|x64
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
{95A4B53D-2773-4406-A2C1-8FD2840BBAD8}.Release|Win32.ActiveCfg = Release|Win32
{95A4B53D-2773-4406-A2C1-8FD2840BBAD8}.Release|Win32.Build.0 = Release|Win32
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
{95A4B53D-2773-4406-A2C1-8FD2840BBAD8}.Release_Vulkan|Win32.ActiveCfg = Release_Vulkan|Win32
{95A4B53D-2773-4406-A2C1-8FD2840BBAD8}.Release_Vulkan|Win32.Build.0 = Release_Vulkan|Win32
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
{95A4B53D-2773-4406-A2C1-8FD2840BBAD8}.Release|x64.ActiveCfg = Release|x64
{95A4B53D-2773-4406-A2C1-8FD2840BBAD8}.Release|x64.Build.0 = Release|x64
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
{95A4B53D-2773-4406-A2C1-8FD2840BBAD8}.Release_Vulkan|x64.ActiveCfg = Release_Vulkan|x64
{95A4B53D-2773-4406-A2C1-8FD2840BBAD8}.Release_Vulkan|x64.Build.0 = Release_Vulkan|x64
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
{BDAE6DE2-6BCC-4107-94F0-DA12214A02DE}.Debug|Win32.ActiveCfg = Debug|Win32
{BDAE6DE2-6BCC-4107-94F0-DA12214A02DE}.Debug|Win32.Build.0 = Debug|Win32
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
{BDAE6DE2-6BCC-4107-94F0-DA12214A02DE}.Debug_Vulkan|Win32.ActiveCfg = Debug|Win32
{BDAE6DE2-6BCC-4107-94F0-DA12214A02DE}.Debug_Vulkan|Win32.Build.0 = Debug|Win32
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
{BDAE6DE2-6BCC-4107-94F0-DA12214A02DE}.Debug|x64.ActiveCfg = Debug|x64
{BDAE6DE2-6BCC-4107-94F0-DA12214A02DE}.Debug|x64.Build.0 = Debug|x64
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
{BDAE6DE2-6BCC-4107-94F0-DA12214A02DE}.Debug_Vulkan|x64.ActiveCfg = Debug|x64
{BDAE6DE2-6BCC-4107-94F0-DA12214A02DE}.Debug_Vulkan|x64.Build.0 = Debug|x64
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
{BDAE6DE2-6BCC-4107-94F0-DA12214A02DE}.Release|Win32.ActiveCfg = Release|Win32
{BDAE6DE2-6BCC-4107-94F0-DA12214A02DE}.Release|Win32.Build.0 = Release|Win32
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
{BDAE6DE2-6BCC-4107-94F0-DA12214A02DE}.Release_Vulkan|Win32.ActiveCfg = Release|Win32
{BDAE6DE2-6BCC-4107-94F0-DA12214A02DE}.Release_Vulkan|Win32.Build.0 = Release|Win32
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
{BDAE6DE2-6BCC-4107-94F0-DA12214A02DE}.Release|x64.ActiveCfg = Release|x64
{BDAE6DE2-6BCC-4107-94F0-DA12214A02DE}.Release|x64.Build.0 = Release|x64
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
{BDAE6DE2-6BCC-4107-94F0-DA12214A02DE}.Release_Vulkan|x64.ActiveCfg = Release|x64
{BDAE6DE2-6BCC-4107-94F0-DA12214A02DE}.Release_Vulkan|x64.Build.0 = Release|x64
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
{BE6B4973-C6FF-4C8F-8E97-A47793C50F44}.Debug|Win32.ActiveCfg = Debug|Win32
{BE6B4973-C6FF-4C8F-8E97-A47793C50F44}.Debug|Win32.Build.0 = Debug|Win32
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
{BE6B4973-C6FF-4C8F-8E97-A47793C50F44}.Debug_Vulkan|Win32.ActiveCfg = Debug|Win32
{BE6B4973-C6FF-4C8F-8E97-A47793C50F44}.Debug_Vulkan|Win32.Build.0 = Debug|Win32
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
{BE6B4973-C6FF-4C8F-8E97-A47793C50F44}.Debug|x64.ActiveCfg = Debug|x64
{BE6B4973-C6FF-4C8F-8E97-A47793C50F44}.Debug|x64.Build.0 = Debug|x64
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
{BE6B4973-C6FF-4C8F-8E97-A47793C50F44}.Debug_Vulkan|x64.ActiveCfg = Debug|x64
{BE6B4973-C6FF-4C8F-8E97-A47793C50F44}.Debug_Vulkan|x64.Build.0 = Debug|x64
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
{BE6B4973-C6FF-4C8F-8E97-A47793C50F44}.Release|Win32.ActiveCfg = Release|Win32
{BE6B4973-C6FF-4C8F-8E97-A47793C50F44}.Release|Win32.Build.0 = Release|Win32
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
{BE6B4973-C6FF-4C8F-8E97-A47793C50F44}.Release_Vulkan|Win32.ActiveCfg = Release|Win32
{BE6B4973-C6FF-4C8F-8E97-A47793C50F44}.Release_Vulkan|Win32.Build.0 = Release|Win32
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
{BE6B4973-C6FF-4C8F-8E97-A47793C50F44}.Release|x64.ActiveCfg = Release|x64
{BE6B4973-C6FF-4C8F-8E97-A47793C50F44}.Release|x64.Build.0 = Release|x64
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
{BE6B4973-C6FF-4C8F-8E97-A47793C50F44}.Release_Vulkan|x64.ActiveCfg = Release|x64
{BE6B4973-C6FF-4C8F-8E97-A47793C50F44}.Release_Vulkan|x64.Build.0 = Release|x64
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
{343333C4-D46C-4C97-A986-959CCA6F1DE0}.Debug|Win32.ActiveCfg = Debug|Win32
{343333C4-D46C-4C97-A986-959CCA6F1DE0}.Debug|Win32.Build.0 = Debug|Win32
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
{343333C4-D46C-4C97-A986-959CCA6F1DE0}.Debug_Vulkan|Win32.ActiveCfg = Debug|Win32
{343333C4-D46C-4C97-A986-959CCA6F1DE0}.Debug_Vulkan|Win32.Build.0 = Debug|Win32
{343333C4-D46C-4C97-A986-959CCA6F1DE0}.Debug_Vulkan|x64.ActiveCfg = Debug|x64
{343333C4-D46C-4C97-A986-959CCA6F1DE0}.Debug_Vulkan|x64.Build.0 = Debug|x64
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
{343333C4-D46C-4C97-A986-959CCA6F1DE0}.Debug|x64.ActiveCfg = Debug|x64
{343333C4-D46C-4C97-A986-959CCA6F1DE0}.Debug|x64.Build.0 = Debug|x64
{343333C4-D46C-4C97-A986-959CCA6F1DE0}.Release|Win32.ActiveCfg = Release|Win32
{343333C4-D46C-4C97-A986-959CCA6F1DE0}.Release|Win32.Build.0 = Release|Win32
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
{343333C4-D46C-4C97-A986-959CCA6F1DE0}.Release_Vulkan|Win32.ActiveCfg = Release|Win32
{343333C4-D46C-4C97-A986-959CCA6F1DE0}.Release_Vulkan|Win32.Build.0 = Release|Win32
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
{343333C4-D46C-4C97-A986-959CCA6F1DE0}.Release|x64.ActiveCfg = Release|x64
{343333C4-D46C-4C97-A986-959CCA6F1DE0}.Release|x64.Build.0 = Release|x64
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
{343333C4-D46C-4C97-A986-959CCA6F1DE0}.Release_Vulkan|x64.ActiveCfg = Release|x64
{343333C4-D46C-4C97-A986-959CCA6F1DE0}.Release_Vulkan|x64.Build.0 = Release|x64
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
{F280BF1A-777A-4FB5-8005-DFBE04621EDB}.Debug|Win32.ActiveCfg = Debug|Win32
{F280BF1A-777A-4FB5-8005-DFBE04621EDB}.Debug|Win32.Build.0 = Debug|Win32
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
{F280BF1A-777A-4FB5-8005-DFBE04621EDB}.Debug_Vulkan|Win32.ActiveCfg = Debug|Win32
{F280BF1A-777A-4FB5-8005-DFBE04621EDB}.Debug_Vulkan|Win32.Build.0 = Debug|Win32
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
{F280BF1A-777A-4FB5-8005-DFBE04621EDB}.Debug|x64.ActiveCfg = Debug|x64
{F280BF1A-777A-4FB5-8005-DFBE04621EDB}.Debug|x64.Build.0 = Debug|x64
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
{F280BF1A-777A-4FB5-8005-DFBE04621EDB}.Debug_Vulkan|x64.ActiveCfg = Debug|x64
{F280BF1A-777A-4FB5-8005-DFBE04621EDB}.Debug_Vulkan|x64.Build.0 = Debug|x64
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
{F280BF1A-777A-4FB5-8005-DFBE04621EDB}.Release|Win32.ActiveCfg = Release|Win32
{F280BF1A-777A-4FB5-8005-DFBE04621EDB}.Release|Win32.Build.0 = Release|Win32
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
{F280BF1A-777A-4FB5-8005-DFBE04621EDB}.Release_Vulkan|Win32.ActiveCfg = Release|Win32
{F280BF1A-777A-4FB5-8005-DFBE04621EDB}.Release_Vulkan|Win32.Build.0 = Release|Win32
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
{F280BF1A-777A-4FB5-8005-DFBE04621EDB}.Release|x64.ActiveCfg = Release|x64
{F280BF1A-777A-4FB5-8005-DFBE04621EDB}.Release|x64.Build.0 = Release|x64
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
{F280BF1A-777A-4FB5-8005-DFBE04621EDB}.Release_Vulkan|x64.ActiveCfg = Release|x64
{F280BF1A-777A-4FB5-8005-DFBE04621EDB}.Release_Vulkan|x64.Build.0 = Release|x64
MSVC builds: Build more tools in gtk/ Build the gtk-update-icon-cache, gtk-builder-tool and gtk-query-settings tools and run gtk-update-icon-cache as part of the post-build "installation" process. Pointed out (and reminded) by Paolo Borelli in bug 759436 that we should build, "install" and run gtk-update-icon-cache in the MSVC builds as well.
2015-12-15 07:37:33 +00:00
{FC98AF16-4C68-42DF-906B-93A6804C198A}.Debug|Win32.ActiveCfg = Debug|Win32
{FC98AF16-4C68-42DF-906B-93A6804C198A}.Debug|Win32.Build.0 = Debug|Win32
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
{FC98AF16-4C68-42DF-906B-93A6804C198A}.Debug_Vulkan|Win32.ActiveCfg = Debug|Win32
{FC98AF16-4C68-42DF-906B-93A6804C198A}.Debug_Vulkan|Win32.Build.0 = Debug|Win32
MSVC builds: Build more tools in gtk/ Build the gtk-update-icon-cache, gtk-builder-tool and gtk-query-settings tools and run gtk-update-icon-cache as part of the post-build "installation" process. Pointed out (and reminded) by Paolo Borelli in bug 759436 that we should build, "install" and run gtk-update-icon-cache in the MSVC builds as well.
2015-12-15 07:37:33 +00:00
{FC98AF16-4C68-42DF-906B-93A6804C198A}.Debug|x64.ActiveCfg = Debug|x64
{FC98AF16-4C68-42DF-906B-93A6804C198A}.Debug|x64.Build.0 = Debug|x64
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
{FC98AF16-4C68-42DF-906B-93A6804C198A}.Debug_Vulkan|x64.ActiveCfg = Debug|x64
{FC98AF16-4C68-42DF-906B-93A6804C198A}.Debug_Vulkan|x64.Build.0 = Debug|x64
MSVC builds: Build more tools in gtk/ Build the gtk-update-icon-cache, gtk-builder-tool and gtk-query-settings tools and run gtk-update-icon-cache as part of the post-build "installation" process. Pointed out (and reminded) by Paolo Borelli in bug 759436 that we should build, "install" and run gtk-update-icon-cache in the MSVC builds as well.
2015-12-15 07:37:33 +00:00
{FC98AF16-4C68-42DF-906B-93A6804C198A}.Release|Win32.ActiveCfg = Release|Win32
{FC98AF16-4C68-42DF-906B-93A6804C198A}.Release|Win32.Build.0 = Release|Win32
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
{FC98AF16-4C68-42DF-906B-93A6804C198A}.Release_Vulkan|Win32.ActiveCfg = Release|Win32
{FC98AF16-4C68-42DF-906B-93A6804C198A}.Release_Vulkan|Win32.Build.0 = Release|Win32
MSVC builds: Build more tools in gtk/ Build the gtk-update-icon-cache, gtk-builder-tool and gtk-query-settings tools and run gtk-update-icon-cache as part of the post-build "installation" process. Pointed out (and reminded) by Paolo Borelli in bug 759436 that we should build, "install" and run gtk-update-icon-cache in the MSVC builds as well.
2015-12-15 07:37:33 +00:00
{FC98AF16-4C68-42DF-906B-93A6804C198A}.Release|x64.ActiveCfg = Release|x64
{FC98AF16-4C68-42DF-906B-93A6804C198A}.Release|x64.Build.0 = Release|x64
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
{FC98AF16-4C68-42DF-906B-93A6804C198A}.Release_Vulkan|x64.ActiveCfg = Release|x64
{FC98AF16-4C68-42DF-906B-93A6804C198A}.Release_Vulkan|x64.Build.0 = Release|x64
MSVC builds: Build more tools in gtk/ Build the gtk-update-icon-cache, gtk-builder-tool and gtk-query-settings tools and run gtk-update-icon-cache as part of the post-build "installation" process. Pointed out (and reminded) by Paolo Borelli in bug 759436 that we should build, "install" and run gtk-update-icon-cache in the MSVC builds as well.
2015-12-15 07:37:33 +00:00
{7D2397CF-4C25-45BC-A1BB-CB4B6E154BBD}.Debug|Win32.ActiveCfg = Debug|Win32
{7D2397CF-4C25-45BC-A1BB-CB4B6E154BBD}.Debug|Win32.Build.0 = Debug|Win32
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
{7D2397CF-4C25-45BC-A1BB-CB4B6E154BBD}.Debug_Vulkan|Win32.ActiveCfg = Debug|Win32
{7D2397CF-4C25-45BC-A1BB-CB4B6E154BBD}.Debug_Vulkan|Win32.Build.0 = Debug|Win32
MSVC builds: Build more tools in gtk/ Build the gtk-update-icon-cache, gtk-builder-tool and gtk-query-settings tools and run gtk-update-icon-cache as part of the post-build "installation" process. Pointed out (and reminded) by Paolo Borelli in bug 759436 that we should build, "install" and run gtk-update-icon-cache in the MSVC builds as well.
2015-12-15 07:37:33 +00:00
{7D2397CF-4C25-45BC-A1BB-CB4B6E154BBD}.Debug|x64.ActiveCfg = Debug|x64
{7D2397CF-4C25-45BC-A1BB-CB4B6E154BBD}.Debug|x64.Build.0 = Debug|x64
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
{7D2397CF-4C25-45BC-A1BB-CB4B6E154BBD}.Debug_Vulkan|x64.ActiveCfg = Debug|x64
{7D2397CF-4C25-45BC-A1BB-CB4B6E154BBD}.Debug_Vulkan|x64.Build.0 = Debug|x64
MSVC builds: Build more tools in gtk/ Build the gtk-update-icon-cache, gtk-builder-tool and gtk-query-settings tools and run gtk-update-icon-cache as part of the post-build "installation" process. Pointed out (and reminded) by Paolo Borelli in bug 759436 that we should build, "install" and run gtk-update-icon-cache in the MSVC builds as well.
2015-12-15 07:37:33 +00:00
{7D2397CF-4C25-45BC-A1BB-CB4B6E154BBD}.Release|Win32.ActiveCfg = Release|Win32
{7D2397CF-4C25-45BC-A1BB-CB4B6E154BBD}.Release|Win32.Build.0 = Release|Win32
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
{7D2397CF-4C25-45BC-A1BB-CB4B6E154BBD}.Release_Vulkan|Win32.ActiveCfg = Release|Win32
{7D2397CF-4C25-45BC-A1BB-CB4B6E154BBD}.Release_Vulkan|Win32.Build.0 = Release|Win32
MSVC builds: Build more tools in gtk/ Build the gtk-update-icon-cache, gtk-builder-tool and gtk-query-settings tools and run gtk-update-icon-cache as part of the post-build "installation" process. Pointed out (and reminded) by Paolo Borelli in bug 759436 that we should build, "install" and run gtk-update-icon-cache in the MSVC builds as well.
2015-12-15 07:37:33 +00:00
{7D2397CF-4C25-45BC-A1BB-CB4B6E154BBD}.Release|x64.ActiveCfg = Release|x64
{7D2397CF-4C25-45BC-A1BB-CB4B6E154BBD}.Release|x64.Build.0 = Release|x64
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
{7D2397CF-4C25-45BC-A1BB-CB4B6E154BBD}.Release_Vulkan|x64.ActiveCfg = Release|x64
{7D2397CF-4C25-45BC-A1BB-CB4B6E154BBD}.Release_Vulkan|x64.Build.0 = Release|x64
MSVC builds: Build more tools in gtk/ Build the gtk-update-icon-cache, gtk-builder-tool and gtk-query-settings tools and run gtk-update-icon-cache as part of the post-build "installation" process. Pointed out (and reminded) by Paolo Borelli in bug 759436 that we should build, "install" and run gtk-update-icon-cache in the MSVC builds as well.
2015-12-15 07:37:33 +00:00
{9F22107A-3EF7-4B52-B269-747B65307F36}.Debug|Win32.ActiveCfg = Debug|Win32
{9F22107A-3EF7-4B52-B269-747B65307F36}.Debug|Win32.Build.0 = Debug|Win32
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
{9F22107A-3EF7-4B52-B269-747B65307F36}.Debug_Vulkan|Win32.ActiveCfg = Debug|Win32
{9F22107A-3EF7-4B52-B269-747B65307F36}.Debug_Vulkan|Win32.Build.0 = Debug|Win32
MSVC builds: Build more tools in gtk/ Build the gtk-update-icon-cache, gtk-builder-tool and gtk-query-settings tools and run gtk-update-icon-cache as part of the post-build "installation" process. Pointed out (and reminded) by Paolo Borelli in bug 759436 that we should build, "install" and run gtk-update-icon-cache in the MSVC builds as well.
2015-12-15 07:37:33 +00:00
{9F22107A-3EF7-4B52-B269-747B65307F36}.Debug|x64.ActiveCfg = Debug|x64
{9F22107A-3EF7-4B52-B269-747B65307F36}.Debug|x64.Build.0 = Debug|x64
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
{9F22107A-3EF7-4B52-B269-747B65307F36}.Debug_Vulkan|x64.ActiveCfg = Debug|x64
{9F22107A-3EF7-4B52-B269-747B65307F36}.Debug_Vulkan|x64.Build.0 = Debug|x64
MSVC builds: Build more tools in gtk/ Build the gtk-update-icon-cache, gtk-builder-tool and gtk-query-settings tools and run gtk-update-icon-cache as part of the post-build "installation" process. Pointed out (and reminded) by Paolo Borelli in bug 759436 that we should build, "install" and run gtk-update-icon-cache in the MSVC builds as well.
2015-12-15 07:37:33 +00:00
{9F22107A-3EF7-4B52-B269-747B65307F36}.Release|Win32.ActiveCfg = Release|Win32
{9F22107A-3EF7-4B52-B269-747B65307F36}.Release|Win32.Build.0 = Release|Win32
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
{9F22107A-3EF7-4B52-B269-747B65307F36}.Release_Vulkan|Win32.ActiveCfg = Release|Win32
{9F22107A-3EF7-4B52-B269-747B65307F36}.Release_Vulkan|Win32.Build.0 = Release|Win32
MSVC builds: Build more tools in gtk/ Build the gtk-update-icon-cache, gtk-builder-tool and gtk-query-settings tools and run gtk-update-icon-cache as part of the post-build "installation" process. Pointed out (and reminded) by Paolo Borelli in bug 759436 that we should build, "install" and run gtk-update-icon-cache in the MSVC builds as well.
2015-12-15 07:37:33 +00:00
{9F22107A-3EF7-4B52-B269-747B65307F36}.Release|x64.ActiveCfg = Release|x64
{9F22107A-3EF7-4B52-B269-747B65307F36}.Release|x64.Build.0 = Release|x64
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
{9F22107A-3EF7-4B52-B269-747B65307F36}.Release_Vulkan|x64.ActiveCfg = Release|x64
{9F22107A-3EF7-4B52-B269-747B65307F36}.Release_Vulkan|x64.Build.0 = Release|x64
{23BBF35F-78AF-4E8C-983F-7B90448CD7DF}.Debug|Win32.ActiveCfg = Debug|Win32
{23BBF35F-78AF-4E8C-983F-7B90448CD7DF}.Debug|Win32.Build.0 = Debug|Win32
{23BBF35F-78AF-4E8C-983F-7B90448CD7DF}.Debug_Vulkan|Win32.ActiveCfg = Debug_Vulkan|Win32
{23BBF35F-78AF-4E8C-983F-7B90448CD7DF}.Debug_Vulkan|Win32.Build.0 = Debug_Vulkan|Win32
{23BBF35F-78AF-4E8C-983F-7B90448CD7DF}.Debug|x64.ActiveCfg = Debug|x64
{23BBF35F-78AF-4E8C-983F-7B90448CD7DF}.Debug|x64.Build.0 = Debug|x64
{23BBF35F-78AF-4E8C-983F-7B90448CD7DF}.Debug_Vulkan|x64.ActiveCfg = Debug_Vulkan|x64
{23BBF35F-78AF-4E8C-983F-7B90448CD7DF}.Debug_Vulkan|x64.Build.0 = Debug_Vulkan|x64
{23BBF35F-78AF-4E8C-983F-7B90448CD7DF}.Release|Win32.ActiveCfg = Release|Win32
{23BBF35F-78AF-4E8C-983F-7B90448CD7DF}.Release|Win32.Build.0 = Release|Win32
{23BBF35F-78AF-4E8C-983F-7B90448CD7DF}.Release_Vulkan|Win32.ActiveCfg = Release_Vulkan|Win32
{23BBF35F-78AF-4E8C-983F-7B90448CD7DF}.Release_Vulkan|Win32.Build.0 = Release_Vulkan|Win32
{23BBF35F-78AF-4E8C-983F-7B90448CD7DF}.Release|x64.ActiveCfg = Release|x64
{23BBF35F-78AF-4E8C-983F-7B90448CD7DF}.Release|x64.Build.0 = Release|x64
{23BBF35F-78AF-4E8C-983F-7B90448CD7DF}.Release_Vulkan|x64.ActiveCfg = Release_Vulkan|x64
{23BBF35F-78AF-4E8C-983F-7B90448CD7DF}.Release_Vulkan|x64.Build.0 = Release_Vulkan|x64
Re-attempt to correct EOL on VS2010 solution This time I realized that I needed to set autocrlf=false on my Windows side ... ugh... This is one of those files that must have CRLF line endings to work correctly :|
2011-06-29 04:49:14 +00:00
EndGlobalSection
GlobalSection(SolutionProperties) = preSolution
HideSolutionNode = FALSE
EndGlobalSection
EndGlobal
Reference in New Issue Copy Permalink