AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity
0b129f3534
gtk2/build/win32/vs12/Makefile.am

52 lines
1.3 KiB
Makefile
Raw Normal View History

Build: Provide Simple Support for MSVC 2012/2013 As the Visual Studio 2012/2013 are only slightly different from the Visual Studio 2010 projects, we can provide support for them by using scripts to copy the Visual Studio 2010 projects, and update the specific parts as necessary. Thus, there would be little maintenance overhead for these as only the 2010 projects need to be kept up-to-date as a result. This might change when we do get the stack working with WinRT/Metro, but that's going to be another totally different issue.
2014-07-01 08:17:43 +00:00
include $(top_srcdir)/Makefile.decl
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.vcxproj \
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
gtk3-prebuild.vcxproj.filters \
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.vcxproj \
gdk3-win32.vcxproj.filters \
gdk-3.vcxproj \
gdk-3.vcxproj.filters \
gtk-3.vcxproj \
gtk-3.vcxproj.filters \
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.vcxproj \
gtk-builder-tool.vcxproj.filters \
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
gtk-encode-symbolic-svg.vcxproj \
gtk-encode-symbolic-svg.vcxproj.filters \
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.vcxproj \
gtk-query-settings.vcxproj.filters \
gtk-update-icon-cache.vcxproj \
gtk-update-icon-cache.vcxproj.filters \
Build: Provide Simple Support for MSVC 2012/2013 As the Visual Studio 2012/2013 are only slightly different from the Visual Studio 2010 projects, we can provide support for them by using scripts to copy the Visual Studio 2010 projects, and update the specific parts as necessary. Thus, there would be little maintenance overhead for these as only the 2010 projects need to be kept up-to-date as a result. This might change when we do get the stack working with WinRT/Metro, but that's going to be another totally different issue.
2014-07-01 08:17:43 +00:00
gtk3-demo.vcxproj \
gtk3-demo.vcxproj.filters \
gtk3-demo-application.vcxproj \
gtk3-demo-application.vcxproj.filters \
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.vcxproj \
gtk3-icon-browser.vcxproj.filters \
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.vcxproj \
gailutil-3.vcxproj.filters \
gtk3-install.vcxproj \
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
gtk3-install.vcxproj.filters \
Build: Provide Simple Support for MSVC 2012/2013 As the Visual Studio 2012/2013 are only slightly different from the Visual Studio 2010 projects, we can provide support for them by using scripts to copy the Visual Studio 2010 projects, and update the specific parts as necessary. Thus, there would be little maintenance overhead for these as only the 2010 projects need to be kept up-to-date as a result. This might change when we do get the stack working with WinRT/Metro, but that's going to be another totally different issue.
2014-07-01 08:17:43 +00:00
broadwayd.vcxproj \
broadwayd.vcxproj.filters \
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.vcxproj \
gdk3-broadway.vcxproj.filters \
gtk3-build-defines.props \
gtk3-copy-gdk-broadway.props \
gtk3-gen-srcs.props \
gtk3-ignore-broadway.props \
gtk3-install.props \
gtk3-version-paths.props
Build: Provide Simple Support for MSVC 2012/2013 As the Visual Studio 2012/2013 are only slightly different from the Visual Studio 2010 projects, we can provide support for them by using scripts to copy the Visual Studio 2010 projects, and update the specific parts as necessary. Thus, there would be little maintenance overhead for these as only the 2010 projects need to be kept up-to-date as a result. This might change when we do get the stack working with WinRT/Metro, but that's going to be another totally different issue.
2014-07-01 08:17:43 +00:00
DISTCLEANFILES = $(EXTRA_DIST)
MSVC_VER = 12
MSVC Builds: "Add" Visual Studio 2015 Projects "Add" Visual Studio 2015 projects by what we did before: Copy the Visual Studio 2010 project files and replace the items in there as needed, as the formats of the 2010 and 2015 projects are largely the same.
2015-09-15 11:40:48 +00:00
MSVC_FORMAT_VER = 12
Build: Provide Simple Support for MSVC 2012/2013 As the Visual Studio 2012/2013 are only slightly different from the Visual Studio 2010 projects, we can provide support for them by using scripts to copy the Visual Studio 2010 projects, and update the specific parts as necessary. Thus, there would be little maintenance overhead for these as only the 2010 projects need to be kept up-to-date as a result. This might change when we do get the stack working with WinRT/Metro, but that's going to be another totally different issue.
2014-07-01 08:17:43 +00:00
MSVC_VER_LONG = 2013
include $(top_srcdir)/build/Makefile-newvs.am
-include $(top_srcdir)/git.mk
Reference in New Issue Copy Permalink