AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity
a65fbf2d49
gtk2/win32/vs12/gtk4-install.propsin

144 lines
7.7 KiB
Plaintext
Raw Normal View History

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
<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<ImportGroup Label="PropertySheets">
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" />
MSVC Builds: Massive Rename of Projects We need to rename the projects so that when these projects are added into an all-in-one solution file that will build the GTK+ 2/3 stack, the names of the projects will not collide with the GTK+-2.x ones, especially as GTK+-2.x and GTK+-3.x are done to co-exist on the same system. This is due to the case that the MSVC projects are directly carried over from the GTK+-2.x ones and was then updated for 3.x. We still need to update the GUIDs of the projects, so that they won't conflict with the GTK+-2.x ones.
2015-08-25 09:41:55 +00:00
</ImportGroup>
<PropertyGroup Label="UserMacros">
<BinDir>$(SolutionDir)$(Configuration)\$(Platform)\bin</BinDir>
<GtkDoInstallBin>
mkdir $(CopyDir)\bin
Visual Studio builds: Generate .pc files Generate .pc files for the package, so that it would be easier for building introspection for packages that depend on GTK+. Also split PythonPath into PythonPath and PythonPathX64 to facilitate the build of introspection files, which need to have Python that is built with the same ac=rchitecture where GTK+ is built. Clean up the formatting and spacing a bit.
2016-04-26 08:27:32 +00:00
mkdir $(CopyDir)\lib\pkgconfig
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
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
if "$(Configuration)" == "Release_Vulkan" goto DO_VULKAN_RELEASE
if "$(Configuration)" == "Debug_Vulkan" goto DO_VULKAN_DEBUG
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
copy "$(BinDir)\$(GtkDllPrefix)gtk-$(ApiVersionShort)$(GtkDllSuffix).dll" $(CopyDir)\bin
copy "$(BinDir)\$(GtkDllPrefix)gtk-$(ApiVersionShort)$(GtkDllSuffix).pdb" $(CopyDir)\bin
copy "$(BinDir)\gtk-$(ApiVersionShort).lib" $(CopyDir)\lib
copy "$(BinDir)\gtk$(ApiVersionShort)-demo.exe" $(CopyDir)\bin
copy "$(BinDir)\gtk$(ApiVersionShort)-demo.pdb" $(CopyDir)\bin
copy "$(BinDir)\gtk$(ApiVersionShort)-demo-application.exe" $(CopyDir)\bin
copy "$(BinDir)\gtk$(ApiVersionShort)-demo-application.pdb" $(CopyDir)\bin
copy "$(BinDir)\gtk$(ApiVersionShort)-icon-browser.exe" $(CopyDir)\bin
copy "$(BinDir)\gtk$(ApiVersionShort)-icon-browser.pdb" $(CopyDir)\bin
copy "$(BinDir)\gtk$(ApiVersionShort)-encode-symbolic-svg.exe" $(CopyDir)\bin
copy "$(BinDir)\gtk$(ApiVersionShort)-encode-symbolic-svg.pdb" $(CopyDir)\bin
copy "$(BinDir)\gtk$(ApiVersionShort)-update-icon-cache.exe" $(CopyDir)\bin
copy "$(BinDir)\gtk$(ApiVersionShort)-update-icon-cache.pdb" $(CopyDir)\bin
copy "$(BinDir)\gtk$(ApiVersionShort)-query-settings.exe" $(CopyDir)\bin
copy "$(BinDir)\gtk$(ApiVersionShort)-query-settings.pdb" $(CopyDir)\bin
copy "$(BinDir)\gtk$(ApiVersionShort)-builder-tool.exe" $(CopyDir)\bin
copy "$(BinDir)\gtk$(ApiVersionShort)-builder-tool.pdb" $(CopyDir)\bin
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
:DO_VULKAN_RELEASE
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
copy .\Release\$(Platform)\bin\$(GtkDllPrefix)gtk-$(ApiVersionShort)$(GtkDllSuffix).dll $(CopyDir)\bin
copy .\Release\$(Platform)\bin\$(GtkDllPrefix)gtk-$(ApiVersionShort)$(GtkDllSuffix).pdb $(CopyDir)\bin
Visual Studio builds: Use gtk-4.lib for the .lib file As with the autotools builds, use gtk-4 as the name of the .lib file that is produced from the build. Actually this is already done with GTK-3.x with the autotools builds, but this update is not done there as gtk-3.0.lib/gdk-3.0.lib/gailutil-3.0.lib was used for such a long time that changing it there might have caused trouble for people there.
2016-11-03 09:46:32 +00:00
copy .\Release\$(Platform)\bin\gtk-$(ApiVersionShort).lib $(CopyDir)\lib
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
copy .\Release\$(Platform)\bin\gtk$(ApiVersionShort)-demo.exe $(CopyDir)\bin
copy .\Release\$(Platform)\bin\gtk$(ApiVersionShort)-demo.pdb $(CopyDir)\bin
copy .\Release\$(Platform)\bin\gtk$(ApiVersionShort)-demo-application.exe $(CopyDir)\bin
copy .\Release\$(Platform)\bin\gtk$(ApiVersionShort)-demo-application.pdb $(CopyDir)\bin
copy .\Release\$(Platform)\bin\gtk$(ApiVersionShort)-icon-browser.exe $(CopyDir)\bin
copy .\Release\$(Platform)\bin\gtk$(ApiVersionShort)-icon-browser.pdb $(CopyDir)\bin
copy .\Release\$(Platform)\bin\gtk$(ApiVersionShort)-encode-symbolic-svg.exe $(CopyDir)\bin
copy .\Release\$(Platform)\bin\gtk$(ApiVersionShort)-encode-symbolic-svg.pdb $(CopyDir)\bin
copy .\Release\$(Platform)\bin\gtk$(ApiVersionShort)-update-icon-cache.exe $(CopyDir)\bin
copy .\Release\$(Platform)\bin\gtk$(ApiVersionShort)-update-icon-cache.pdb $(CopyDir)\bin
copy .\Release\$(Platform)\bin\gtk$(ApiVersionShort)-query-settings.exe $(CopyDir)\bin
copy .\Release\$(Platform)\bin\gtk$(ApiVersionShort)-query-settings.pdb $(CopyDir)\bin
copy .\Release\$(Platform)\bin\gtk$(ApiVersionShort)-builder-tool.exe $(CopyDir)\bin
copy .\Release\$(Platform)\bin\gtk$(ApiVersionShort)-builder-tool.pdb $(CopyDir)\bin
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
goto DONE_BIN
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
:DO_VULKAN_DEBUG
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
copy .\Debug\$(Platform)\bin\$(GtkDllPrefix)gtk-$(ApiVersionShort)$(GtkDllSuffix).dll $(CopyDir)\bin
copy .\Debug\$(Platform)\bin\$(GtkDllPrefix)gtk-$(ApiVersionShort)$(GtkDllSuffix).pdb $(CopyDir)\bin
Visual Studio builds: Use gtk-4.lib for the .lib file As with the autotools builds, use gtk-4 as the name of the .lib file that is produced from the build. Actually this is already done with GTK-3.x with the autotools builds, but this update is not done there as gtk-3.0.lib/gdk-3.0.lib/gailutil-3.0.lib was used for such a long time that changing it there might have caused trouble for people there.
2016-11-03 09:46:32 +00:00
copy .\Debug\$(Platform)\bin\gtk-$(ApiVersionShort).lib $(CopyDir)\lib
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
copy .\Debug\$(Platform)\bin\gtk$(ApiVersionShort)-demo.exe $(CopyDir)\bin
copy .\Debug\$(Platform)\bin\gtk$(ApiVersionShort)-demo.pdb $(CopyDir)\bin
copy .\Debug\$(Platform)\bin\gtk$(ApiVersionShort)-demo-application.exe $(CopyDir)\bin
copy .\Debug\$(Platform)\bin\gtk$(ApiVersionShort)-demo-application.pdb $(CopyDir)\bin
copy .\Debug\$(Platform)\bin\gtk$(ApiVersionShort)-icon-browser.exe $(CopyDir)\bin
copy .\Debug\$(Platform)\bin\gtk$(ApiVersionShort)-icon-browser.pdb $(CopyDir)\bin
copy .\Debug\$(Platform)\bin\gtk$(ApiVersionShort)-encode-symbolic-svg.exe $(CopyDir)\bin
copy .\Debug\$(Platform)\bin\gtk$(ApiVersionShort)-encode-symbolic-svg.pdb $(CopyDir)\bin
copy .\Debug\$(Platform)\bin\gtk$(ApiVersionShort)-update-icon-cache.exe $(CopyDir)\bin
copy .\Debug\$(Platform)\bin\gtk$(ApiVersionShort)-update-icon-cache.pdb $(CopyDir)\bin
copy .\Debug\$(Platform)\bin\gtk$(ApiVersionShort)-query-settings.exe $(CopyDir)\bin
copy .\Debug\$(Platform)\bin\gtk$(ApiVersionShort)-query-settings.pdb $(CopyDir)\bin
copy .\Debug\$(Platform)\bin\gtk$(ApiVersionShort)-builder-tool.exe $(CopyDir)\bin
copy .\Debug\$(Platform)\bin\gtk$(ApiVersionShort)-builder-tool.pdb $(CopyDir)\bin
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
:DONE_BIN
Visual Studio builds: Generate .pc files Generate .pc files for the package, so that it would be easier for building introspection for packages that depend on GTK+. Also split PythonPath into PythonPath and PythonPathX64 to facilitate the build of introspection files, which need to have Python that is built with the same ac=rchitecture where GTK+ is built. Clean up the formatting and spacing a bit.
2016-04-26 08:27:32 +00:00
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
copy "..\gtk+-$(ApiVersion).pc" $(CopyDir)\lib\pkgconfig
copy "..\gtk+-$(ApiVersion).pc" "$(CopyDir)\lib\pkgconfig\gtk+-win32-$(ApiVersion).pc"
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
</GtkDoInstallBin>
<GtkDoInstall>
echo off
mkdir $(CopyDir)\include\gtk-$(ApiVersion)\gdk\win32
mkdir $(CopyDir)\include\gtk-$(ApiVersion)\gdk\deprecated
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
copy ..\..\gdk\win32\gdkwin32.h $(CopyDir)\include\gtk-$(ApiVersion)\gdk
MSVC builds: Support MSVC 2013 and later We now need C99 features from the compiler which are only supported by Visual Studio 2013 and later, so drop the MSVC 2008~2012 projects, and make the baseline supported Visual Studio version be 2013. Update the build files as a result.
2016-10-26 05:42:43 +00:00
#include "gdk-4.vs12.headers"
#include "gdk4-win32.vs12.headers"
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
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
mkdir $(CopyDir)\include\gtk-$(ApiVersion)\gsk
#include "gsk-4.vs12.headers"
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
mkdir $(CopyDir)\include\gtk-$(ApiVersion)\gtk\a11y
mkdir $(CopyDir)\include\gtk-$(ApiVersion)\gtk\deprecated
MSVC builds: Support MSVC 2013 and later We now need C99 features from the compiler which are only supported by Visual Studio 2013 and later, so drop the MSVC 2008~2012 projects, and make the baseline supported Visual Studio version be 2013. Update the build files as a result.
2016-10-26 05:42:43 +00:00
#include "gtk-4.vs12.headers"
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
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
for &#37;&#37;s in (16 22 24 32 48 256) do ((mkdir $(CopyDir)\share\icons\hicolor\&#37;&#37;sx&#37;&#37;s\apps) &amp; (copy /b ..\..\demos\gtk-demo\data\&#37;&#37;sx&#37;&#37;s\gtk$(ApiVersionShort)-demo.png $(CopyDir)\share\icons\hicolor\&#37;&#37;sx&#37;&#37;s\apps))
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
mkdir $(CopyDir)\share\glib-2.0\schemas
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
copy ..\..\gtk\org.gtk.Settings.FileChooser.gschema.xml $(CopyDir)\share\glib-2.0\schemas
copy ..\..\gtk\org.gtk.Settings.ColorChooser.gschema.xml $(CopyDir)\share\glib-2.0\schemas
copy ..\..\gtk\org.gtk.Settings.Debug.gschema.xml $(CopyDir)\share\glib-2.0\schemas
copy ..\..\demos\gtk-demo\org.gtk.Demo.gschema.xml $(CopyDir)\share\glib-2.0\schemas
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
</GtkDoInstall>
Visual Studio builds: Refine "installation" process Split out the part where we generate/update the caches for the GSchemas and the icons, so that it is easier to ensure that things continue to function correctly when we have GlibEtcInstallRoot != CopyDir.
2016-05-10 05:18:23 +00:00
<GtkPostInstall>
echo "Compiling gsettings XML Files..."
$(GlibEtcInstallRoot)\bin\glib-compile-schemas.exe $(CopyDir)\share\glib-2.0\schemas
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
echo "Generating icon cache..."
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
$(CopyDir)\bin\gtk$(ApiVersionShort)-update-icon-cache.exe --ignore-theme-index --force "$(CopyDir)\share\icons\hicolor"
Visual Studio builds: Refine "installation" process Split out the part where we generate/update the caches for the GSchemas and the icons, so that it is easier to ensure that things continue to function correctly when we have GlibEtcInstallRoot != CopyDir.
2016-05-10 05:18:23 +00:00
</GtkPostInstall>
Visual Studio builds: Generate .pc files Generate .pc files for the package, so that it would be easier for building introspection for packages that depend on GTK+. Also split PythonPath into PythonPath and PythonPathX64 to facilitate the build of introspection files, which need to have Python that is built with the same ac=rchitecture where GTK+ is built. Clean up the formatting and spacing a bit.
2016-04-26 08:27:32 +00:00
<GenerateGtkPC>$(PythonPath)\python ..\gtkpc.py --prefix=$(CopyDir) --version=$(GtkVersion) --host=i686-pc-vs$(VSVer)</GenerateGtkPC>
<GenerateGtkPCX64>$(PythonPathX64)\python ..\gtkpc.py --prefix=$(CopyDir) --version=$(GtkVersion) --host=x86_64-pc-vs$(VSVer)</GenerateGtkPCX64>
Visual Studio builds: Drop the Broadway projects Since the status of the GDK broadway backend is more or less unsupported, drop the projects that build gtk4-broadwayd and gdk-broadway, and update the projects to not to refer to them. However, keep the Broadway configs for now as we will later transform them to become configs for Vulkan, so bascially besides "installation" parts and output settings, they will do the same as their Release|Debug counterparts with no support for Broadway.
2016-12-30 03:09:46 +00:00
<GtkPCFiles>..\gtk+-$(ApiVersion).pc</GtkPCFiles>
MSVC Builds: Massive Rename of Projects We need to rename the projects so that when these projects are added into an all-in-one solution file that will build the GTK+ 2/3 stack, the names of the projects will not collide with the GTK+-2.x ones, especially as GTK+-2.x and GTK+-3.x are done to co-exist on the same system. This is due to the case that the MSVC projects are directly carried over from the GTK+-2.x ones and was then updated for 3.x. We still need to update the GUIDs of the projects, so that they won't conflict with the GTK+-2.x ones.
2015-08-25 09:41:55 +00:00
</PropertyGroup>
<PropertyGroup>
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
<_PropertySheetDisplayName>gtk4installsprops</_PropertySheetDisplayName>
MSVC Builds: Massive Rename of Projects We need to rename the projects so that when these projects are added into an all-in-one solution file that will build the GTK+ 2/3 stack, the names of the projects will not collide with the GTK+-2.x ones, especially as GTK+-2.x and GTK+-3.x are done to co-exist on the same system. This is due to the case that the MSVC projects are directly carried over from the GTK+-2.x ones and was then updated for 3.x. We still need to update the GUIDs of the projects, so that they won't conflict with the GTK+-2.x ones.
2015-08-25 09:41:55 +00:00
</PropertyGroup>
<ItemGroup>
<BuildMacro Include="BinDir">
<Value>$(BinDir)</Value>
</BuildMacro>
<BuildMacro Include="InstalledDlls">
<Value>$(InstalledDlls)</Value>
</BuildMacro>
<BuildMacro Include="InstalledBins">
<Value>$(InstalledBins)</Value>
</BuildMacro>
<BuildMacro Include="GtkDoInstallBin">
<Value>$(GtkDoInstallBin)</Value>
</BuildMacro>
<BuildMacro Include="GtkDoInstall">
<Value>$(GtkDoInstall)</Value>
</BuildMacro>
Visual Studio builds: Refine "installation" process Split out the part where we generate/update the caches for the GSchemas and the icons, so that it is easier to ensure that things continue to function correctly when we have GlibEtcInstallRoot != CopyDir.
2016-05-10 05:18:23 +00:00
<BuildMacro Include="GtkPostInstall">
<Value>$(GtkPostInstall)</Value>
</BuildMacro>
Visual Studio builds: Generate .pc files Generate .pc files for the package, so that it would be easier for building introspection for packages that depend on GTK+. Also split PythonPath into PythonPath and PythonPathX64 to facilitate the build of introspection files, which need to have Python that is built with the same ac=rchitecture where GTK+ is built. Clean up the formatting and spacing a bit.
2016-04-26 08:27:32 +00:00
<BuildMacro Include="GenerateGtkPC">
<Value>$(GenerateGtkPC)</Value>
</BuildMacro>
<BuildMacro Include="GenerateGtkPCX64">
<Value>$(GenerateGtkPCX64)</Value>
</BuildMacro>
<BuildMacro Include="GtkPCFiles">
<Value>$(GtkPCFiles)</Value>
</BuildMacro>
MSVC Builds: Massive Rename of Projects We need to rename the projects so that when these projects are added into an all-in-one solution file that will build the GTK+ 2/3 stack, the names of the projects will not collide with the GTK+-2.x ones, especially as GTK+-2.x and GTK+-3.x are done to co-exist on the same system. This is due to the case that the MSVC projects are directly carried over from the GTK+-2.x ones and was then updated for 3.x. We still need to update the GUIDs of the projects, so that they won't conflict with the GTK+-2.x ones.
2015-08-25 09:41:55 +00:00
</ItemGroup>
</Project>
Reference in New Issue Copy Permalink