AuroraMiddleware/gtk
1
0
Fork 1
mirror of https://gitlab.gnome.org/GNOME/gtk.git synced 2025-01-16 07:04:29 +00:00
Code Issues Projects Releases Wiki Activity
a6b9b3648d
gtk/build/win32/vs9/Makefile.am

56 lines
1.3 KiB
Makefile
Raw Normal View History

Need to include Makefile.decl in the new Makefile.am files Otherwise make check breaks.
2010-04-12 20:47:52 +00:00
include $(top_srcdir)/Makefile.decl
build/win32: Fix 'make -jN dist' The recent changes to build/win32/vs9|10/Makefile.am fixed 'make distclean' but broke 'make -jN dist', so fix that by listing the *.headers and using that list as a dependency and to remove those files in one single command right after we generate the gtk-install.vsprops template, so that we don't have to worry about them in 'make distclean'.
2015-09-23 10:31:22 +00:00
MSVC_HEADERS_LISTS = \
gdk3-win32.headers \
gdk3-broadway.headers \
gdk-3.headers \
gtk-3.headers \
gailutil-3.headers
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
GENERATED_ITEMS = \
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
gdk3-win32.vcproj \
gdk3-broadway.vcproj \
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
broadwayd.vcproj \
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
gdk-3.vcproj \
gtk-3.vcproj \
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
gtk3-demo.vcproj \
Visual Studio Builds: Support Building Introspection Files Add Windows .bat and Python script to call g-ir-scanner to build introspection files for Visual Studio builds. This will read from the autotools files using Python REGEX functionality to determine the headers and sources for g-ir-scanner to process, so the autotools files will not need to be updated except to distribute the necessary files. Thils will also enable one to build introspection files on Windows without using a BASH-style shell such as MSYS. Also add an utility Visual Studio project to call the Windows .bat to build the introspection files for GTK+/GDK, for convenience.
2013-03-06 05:12:01 +00:00
gtk3-demo-application.vcproj \
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
gtk3-icon-browser.vcproj \
Fix distclean
2015-09-22 02:01:59 +00:00
gailutil-3.vcproj \
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
gtk3-install.vsprops \
build/win32: Fix 'make -jN dist' The recent changes to build/win32/vs9|10/Makefile.am fixed 'make distclean' but broke 'make -jN dist', so fix that by listing the *.headers and using that list as a dependency and to remove those files in one single command right after we generate the gtk-install.vsprops template, so that we don't have to worry about them in 'make distclean'.
2015-09-23 10:31:22 +00:00
gtk3-version-paths.vsprops
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
EXTRA_DIST += \
README.txt \
gtk+.sln \
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
gtk3-prebuild.vcproj \
gdk3-win32.vcprojin \
gdk-3.vcprojin \
gtk-3.vcprojin \
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
gtk-builder-tool.vcproj \
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
gtk-encode-symbolic-svg.vcproj \
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
gtk-query-settings.vcproj \
gtk-update-icon-cache.vcproj \
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
gtk3-demo.vcprojin \
gtk3-demo-application.vcprojin \
gtk3-icon-browser.vcprojin \
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
gailutil-3.vcprojin \
gtk3-install.vcproj \
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
broadwayd.vcprojin \
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
gdk3-broadway.vcprojin \
gtk3-build-defines.vsprops \
gtk3-copy-gdk-broadway.vsprops \
gtk3-gen-srcs.vsprops \
gtk3-ignore-broadway.vsprops \
gtk3-install.vspropsin \
gtk3-version-paths.vsprops.in \
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
$(GENERATED_ITEMS)
build/win32: Fix 'make -jN dist' The recent changes to build/win32/vs9|10/Makefile.am fixed 'make distclean' but broke 'make -jN dist', so fix that by listing the *.headers and using that list as a dependency and to remove those files in one single command right after we generate the gtk-install.vsprops template, so that we don't have to worry about them in 'make distclean'.
2015-09-23 10:31:22 +00:00
gtk3-install.vsprops: $(top_srcdir)/build/win32/vs9/gtk3-install.vspropsin $(MSVC_HEADERS_LISTS)
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
$(CPP) -P - <$(top_srcdir)/build/win32/vs9/gtk3-install.vspropsin >$@
build/win32: Fix 'make -jN dist' The recent changes to build/win32/vs9|10/Makefile.am fixed 'make distclean' but broke 'make -jN dist', so fix that by listing the *.headers and using that list as a dependency and to remove those files in one single command right after we generate the gtk-install.vsprops template, so that we don't have to worry about them in 'make distclean'.
2015-09-23 10:31:22 +00:00
rm $(MSVC_HEADERS_LISTS)
build: Clean Up Visual Studio Project Generation Use the common automake module from the previous commit in the Makefile.am's, which means that the Makefile.am's in gdk/ and gtk/ can be cleaned up as a result. As a side effect, the property sheet that is used to "install" the build results and headers can now be generated in terms of the listing of headers to copy during 'make dist', where we can acquire most of the list of headers to "install", so that we can largely avoid the situation where the property sheet files are not updated in time for this, causing missing headers when this build of GTK+ is being used. Also use the Visual Studio Project file generation for the following projects: gtk3-demo gtk3-demo-application gtk3-icon-browser gdk-win32 gdk-broadway gail-util So that the maintenace of these project files can be simplified as well. https://bugzilla.gnome.org/show_bug.cgi?id=681965
2015-04-17 06:47:56 +00:00
DISTCLEANFILES = $(GENERATED_ITEMS)
Add git.mk to more places
2013-01-24 22:35:30 +00:00
-include $(top_srcdir)/git.mk
Reference in New Issue Copy Permalink