AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity
c9a313a125
gtk2/build/win32/vs12/gtk4-gen-srcs.props

99 lines
5.4 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"?>
build/win32/vs12/gtk4-gen-srcs.props: Fix XML reference URL Visual Studio can be picky about this, causing projects not to load.
2016-10-27 04:27:04 +00:00
<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
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 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">
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
<GenConfigH>copy ..\..\..\config.h.win32 ..\..\..\config.h</GenConfigH>
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
<GenGdkConfigHWin32>
if exist ..\..\..\MSVC_$(Configuration) goto DONE_GDKCONFIG_H
if exist ..\..\..\gdk\gdkconfig.h del ..\..\..\gdk\gdkconfig.h
if exist ..\..\..\GDK_BROADWAY_BUILD del ..\..\..\GDK_BROADWAY_BUILD
if exist ..\..\..\MSVC_$(Configuration)_Broadway del ..\..\..\MSVC_$(Configuration)_Broadway
if exist $(Configuration)\$(Platform)\bin\$(GtkDllPrefix)gdk$(GtkDllSuffix).dll del $(Configuration)\$(Platform)\bin\$(GtkDllPrefix)gdk$(GtkDllSuffix).dll
if exist $(Configuration)\$(Platform)\bin\gdk-$(ApiVersion).lib del $(Configuration)\$(Platform)\bin\gdk-$(ApiVersion).lib
if "$(Configuration)" == "Release" del ..\..\..\MSVC_Debug
if "$(Configuration)" == "Debug" del ..\..\..\MSVC_Release
copy ..\..\..\gdk\gdkconfig.h.win32 ..\..\..\gdk\gdkconfig.h
copy ..\..\..\gdk\gdkconfig.h.win32 ..\..\..\GDK_WIN32ONLY_BUILD
echo $(Configuration) &gt; ..\..\..\MSVC_$(Configuration)
:DONE_GDKCONFIG_H
</GenGdkConfigHWin32>
<GenGdkConfigHBroadway>
if exist ..\..\..\MSVC_$(Configuration)_Broadway goto DONE_GDKCONFIG_H
if exist ..\..\..\gdk\gdkconfig.h del ..\..\..\gdk\gdkconfig.h
if exist ..\..\..\GDK_WIN32ONLY_BUILD del ..\..\..\GDK_WIN32ONLY_BUILD
if exist ..\..\..\MSVC_Release del ..\..\..\MSVC_Release
if exist ..\..\..\MSVC_Debug del ..\..\..\MSVC_Debug
if "$(Configuration)" == "Release_Broadway" del ..\..\..\MSVC_Debug_Broadway
if "$(Configuration)" == "Debug_Broadway" del ..\..\..\MSVC_Release_Broadway
copy ..\..\..\gdk\gdkconfig.h.win32_broadway ..\..\..\gdk\gdkconfig.h
copy ..\..\..\gdk\gdkconfig.h.win32_broadway ..\..\..\GDK_BROADWAY_BUILD
echo $(Configuration) &gt; ..\..\..\MSVC_$(Configuration)_Broadway
:DONE_GDKCONFIG_H
</GenGdkConfigHBroadway>
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
<GDbusCodeGenCmd>$(GlibEtcInstallRoot)\bin\gdbus-codegen --interface-prefix org.Gtk. --c-namespace _Gtk --generate-c-code gtkdbusgenerated ./gtkdbusinterfaces.xml</GDbusCodeGenCmd>
<GenerateGtkDbusBuiltSources>cd ..\..\..\gtk &amp; $(PythonPath)\python $(GDbusCodeGenCmd) &amp; cd $(SolutionDir)</GenerateGtkDbusBuiltSources>
<GenerateGtkDbusBuiltSourcesX64>cd ..\..\..\gtk &amp; $(PythonPathX64)\python $(GDbusCodeGenCmd) &amp; cd $(SolutionDir)</GenerateGtkDbusBuiltSourcesX64>
Windows: Update how gtk-win32.rc is generated On Visual Studio, unlike MinGW, manifest files are embedded via including the manifest file as a resource file in the projects, not via the .rc file. This means that the line in the .rc file that specifies the manifest file would cause trouble, so that line gets removed when the full gtk3-win32.rc is generated on Visual Studio builds, otherwise 2010+ Visual Studio will complain when compiling the .rc file. Also, the inclusion of winuser.h will cause warnings during the compilation of the .rc file. Fix this by isolating the Win32 resource portions of gtk-win32.rc.in to gtk-win32.rc.body.in and: -On MinGW, construct the full gtk-win32.rc by doing the winver.h and winuser.h inclusion first, then append the contents of gtk-win32.rc.body, and then appending the line to embed the manifest file. -On Visual Studio, simply copy the gtk-win32.rc.body to gtk-win32.rc, and generate the full libgtk3.manifest file. https://bugzilla.gnome.org/show_bug.cgi?id=762311
2016-02-22 09:38:15 +00:00
<CopyGtkWin32RC>copy ..\..\..\gtk\gtk-win32.rc.body ..\..\..\gtk\gtk-win32.rc</CopyGtkWin32RC>
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
<GenerateGtkWin32Manifest>$(PythonPath)\python ..\replace.py --action=replace-var --input=..\..\..\gtk\libgtk4.manifest.in --output=..\..\..\gtk\libgtk4.manifest --var=EXE_MANIFEST_ARCHITECTURE --outstring=*</GenerateGtkWin32Manifest>
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
<CopyDemosH>copy ..\..\..\demos\gtk-demo\demos.h.win32 ..\..\..\demos\gtk-demo\demos.h</CopyDemosH>
MSVC builds: Make the GSK project functional Add the needed custom build steps to generate the GResource and enumeration sources that is needed for the build, and make sure that the build is able to find the Graphene headers and lib. Also add the necessary CFLAGS needed for building GSK.
2016-10-27 06:13:42 +00:00
<GenGSKEnumSrcs>(cd ..) &amp; (call gen-enums.bat $(GlibEtcInstallRoot)) &amp; (cd $(SolutionDir))</GenGSKEnumSrcs>
<GenGSKRsrcSrcs>
echo ^&lt;?xml version='1.0' encoding='UTF-8'?^&gt; &gt; ..\..\..\gsk\gsk.gresource.xml
echo ^&lt;gresources^&gt; &gt;&gt; ..\..\..\gsk\gsk.gresource.xml
echo ^&lt;gresource prefix='/org/gtk/libgsk'^&gt; &gt;&gt; ..\..\..\gsk\gsk.gresource.xml
for /f &#37;&#37;f in ('dir /b ..\..\..\gsk\resources\glsl\*') do echo ^&lt;file alias='glsl/&#37;&#37;f'^&gt;resources/glsl/&#37;&#37;f^&lt;/file^&gt; &gt;&gt; ..\..\..\gsk\gsk.gresource.xml
echo ^&lt;/gresource^&gt; &gt;&gt; ..\..\..\gsk\gsk.gresource.xml
echo ^&lt;/gresources^&gt; &gt;&gt; ..\..\..\gsk\gsk.gresource.xml
$(GlibEtcInstallRoot)\bin\glib-compile-resources.exe --sourcedir=..\..\..\gsk --c-name _gsk --generate-header --manual-register --target=..\..\..\gsk\gskresources.h ..\..\..\gsk\gsk.gresource.xml
$(GlibEtcInstallRoot)\bin\glib-compile-resources.exe --sourcedir=..\..\..\gsk --c-name _gsk --generate-source --manual-register --target=..\..\..\gsk\gskresources.c ..\..\..\gsk\gsk.gresource.xml
</GenGSKRsrcSrcs>
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>gtk4gensrcsprops</_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="GenConfigH">
<Value>$(GenConfigH)</Value>
</BuildMacro>
<BuildMacro Include="GenGdkConfigHWin32">
<Value>$(GenGdkConfigHWin32)</Value>
</BuildMacro>
<BuildMacro Include="GenGdkConfigHBroadway">
<Value>$(GenGdkConfigHBroadway)</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="GDbusCodeGenCmd">
<Value>$(GDbusCodeGenCmd)</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
<BuildMacro Include="GenerateGtkDbusBuiltSources">
<Value>$(GenerateGtkDbusBuiltSources)</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="GenerateGtkDbusBuiltSourcesX64">
<Value>$(GenerateGtkDbusBuiltSourcesX64)</Value>
</BuildMacro>
Windows: Update how gtk-win32.rc is generated On Visual Studio, unlike MinGW, manifest files are embedded via including the manifest file as a resource file in the projects, not via the .rc file. This means that the line in the .rc file that specifies the manifest file would cause trouble, so that line gets removed when the full gtk3-win32.rc is generated on Visual Studio builds, otherwise 2010+ Visual Studio will complain when compiling the .rc file. Also, the inclusion of winuser.h will cause warnings during the compilation of the .rc file. Fix this by isolating the Win32 resource portions of gtk-win32.rc.in to gtk-win32.rc.body.in and: -On MinGW, construct the full gtk-win32.rc by doing the winver.h and winuser.h inclusion first, then append the contents of gtk-win32.rc.body, and then appending the line to embed the manifest file. -On Visual Studio, simply copy the gtk-win32.rc.body to gtk-win32.rc, and generate the full libgtk3.manifest file. https://bugzilla.gnome.org/show_bug.cgi?id=762311
2016-02-22 09:38:15 +00:00
<BuildMacro Include="CopyGtkWin32RC">
<Value>$(CopyGtkWin32RC)</Value>
</BuildMacro>
<BuildMacro Include="GenerateGtkWin32Manifest">
<Value>$(GenerateGtkWin32Manifest)</Value>
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
</BuildMacro>
<BuildMacro Include="CopyDemosH">
<Value>$(CopyDemosH)</Value>
</BuildMacro>
MSVC builds: Make the GSK project functional Add the needed custom build steps to generate the GResource and enumeration sources that is needed for the build, and make sure that the build is able to find the Graphene headers and lib. Also add the necessary CFLAGS needed for building GSK.
2016-10-27 06:13:42 +00:00
<BuildMacro Include="GenGSKEnumSrcs">
<Value>$(GenGSKEnumSrcs)</Value>
</BuildMacro>
<BuildMacro Include="GenGSKRsrcSrcs">
<Value>$(GenGSKRsrcSrcs)</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