glib/build/Makefile-newvs.am

# Centralized autotools file
# Create the Visual Studio 2012/2013 project files
# from the Visual Studio 2010 project files

# Author: Fan, Chun-wei
# November 05, 2012

# MSVC_SLN: name of root project

MSVC_FORMAT_VER=$(shell echo $$(expr $(MSVC_VER) + 1))

$(MSVC_SLN).sln: $(top_srcdir)/build/win32/vs10/$(MSVC_SLN).sln
	cat $< | sed 's/11\.00/$(MSVC_FORMAT_VER)\.00/g' | sed 's/2010/$(MSVC_VER_LONG)/g' > $(top_builddir)/build/win32/vs$(MSVC_VER)/$@

README.txt: $(top_srcdir)/build/win32/vs10/README.txt
	cat $< | sed 's/vs10/vs$(MSVC_VER)/g' | sed 's/VS10/VS$(MSVC_VER)/g' > $(top_builddir)/build/win32/vs$(MSVC_VER)/$@

%.vcxproj:
	cat $(top_builddir)/build/win32/vs10/$@ | sed 's/v100/v$(MSVC_VER)0/g' > $(top_builddir)/build/win32/vs$(MSVC_VER)/$@

%.props:
	cat $(top_builddir)/build/win32/vs10/$@ | sed 's/<VSVer>10<\/VSVer>/<VSVer>$(MSVC_VER)<\/VSVer>/g' > $(top_builddir)/build/win32/vs$(MSVC_VER)/$@

%.vcxproj.filters:
	cp $(top_builddir)/build/win32/vs10/$@ $(top_builddir)/build/win32/vs$(MSVC_VER)/$@
Add autotools scripts to create VS2012 projects As the project file format for Visual Studio 2012 is only slightly different from Visual Studio 2010 projects, we can provide support for building GLib (and other projects) with Visual Studio 2012 with relatively little effort. This might change when we eventually get GLib to work with the Windows 8 (Modern UI/formerly Metro) APIs, but this will suffice for the time being for people needing to build GLib with Visual Studio 2012. Basically all that needs to be done at 'make dist' is: -Copy the .sln/.props/README.txt/.vcxproj files and replace the VS2010 stuff with VS2012 stuff -Copy the .vcxproj.filters as is 2012-11-19 05:58:55 +01:00			`# Centralized autotools file`
Support Building Using Visual Studio 2013 Like the Visual Studio 2012 project files, the Visual Studio 2013 files are largely the same as the Visual Studio 2010 project files, so support Visual Studio 2013 by updating the autotools scripts that is used for Visual Studio 2012. This means that project files for Visual Studio 2012 and Visual Studio 2013 can be maintained by simply maintaining the Visual Studio 2010 project files, adding minimal maintenance overhead. 2014-06-03 09:50:37 +02:00			`# Create the Visual Studio 2012/2013 project files`
build/Makefile-newvs.am: Make description comment clearer 2013-01-22 07:14:27 +01:00			`# from the Visual Studio 2010 project files`
Add autotools scripts to create VS2012 projects As the project file format for Visual Studio 2012 is only slightly different from Visual Studio 2010 projects, we can provide support for building GLib (and other projects) with Visual Studio 2012 with relatively little effort. This might change when we eventually get GLib to work with the Windows 8 (Modern UI/formerly Metro) APIs, but this will suffice for the time being for people needing to build GLib with Visual Studio 2012. Basically all that needs to be done at 'make dist' is: -Copy the .sln/.props/README.txt/.vcxproj files and replace the VS2010 stuff with VS2012 stuff -Copy the .vcxproj.filters as is 2012-11-19 05:58:55 +01:00
			`# Author: Fan, Chun-wei`
			`# November 05, 2012`

			`# MSVC_SLN: name of root project`

Support Building Using Visual Studio 2013 Like the Visual Studio 2012 project files, the Visual Studio 2013 files are largely the same as the Visual Studio 2010 project files, so support Visual Studio 2013 by updating the autotools scripts that is used for Visual Studio 2012. This means that project files for Visual Studio 2012 and Visual Studio 2013 can be maintained by simply maintaining the Visual Studio 2010 project files, adding minimal maintenance overhead. 2014-06-03 09:50:37 +02:00			`MSVC_FORMAT_VER=$(shell echo $$(expr $(MSVC_VER) + 1))`
Add autotools scripts to create VS2012 projects As the project file format for Visual Studio 2012 is only slightly different from Visual Studio 2010 projects, we can provide support for building GLib (and other projects) with Visual Studio 2012 with relatively little effort. This might change when we eventually get GLib to work with the Windows 8 (Modern UI/formerly Metro) APIs, but this will suffice for the time being for people needing to build GLib with Visual Studio 2012. Basically all that needs to be done at 'make dist' is: -Copy the .sln/.props/README.txt/.vcxproj files and replace the VS2010 stuff with VS2012 stuff -Copy the .vcxproj.filters as is 2012-11-19 05:58:55 +01:00
build/Makfile-newvs.am: Use Pattern Rules Make use of pattern rules when generating the Visual Studio 2012/2013 Projects from the Visual Studio 2010 projects, which will help to clean up the file and also avoid problems when running items like 'make -jN dist'. 2015-04-17 07:59:28 +02:00			`$(MSVC_SLN).sln: $(top_srcdir)/build/win32/vs10/$(MSVC_SLN).sln`
			`cat $< \| sed 's/11\.00/$(MSVC_FORMAT_VER)\.00/g' \| sed 's/2010/$(MSVC_VER_LONG)/g' > $(top_builddir)/build/win32/vs$(MSVC_VER)/$@`
Add autotools scripts to create VS2012 projects As the project file format for Visual Studio 2012 is only slightly different from Visual Studio 2010 projects, we can provide support for building GLib (and other projects) with Visual Studio 2012 with relatively little effort. This might change when we eventually get GLib to work with the Windows 8 (Modern UI/formerly Metro) APIs, but this will suffice for the time being for people needing to build GLib with Visual Studio 2012. Basically all that needs to be done at 'make dist' is: -Copy the .sln/.props/README.txt/.vcxproj files and replace the VS2010 stuff with VS2012 stuff -Copy the .vcxproj.filters as is 2012-11-19 05:58:55 +01:00
			`README.txt: $(top_srcdir)/build/win32/vs10/README.txt`
build/Makfile-newvs.am: Use Pattern Rules Make use of pattern rules when generating the Visual Studio 2012/2013 Projects from the Visual Studio 2010 projects, which will help to clean up the file and also avoid problems when running items like 'make -jN dist'. 2015-04-17 07:59:28 +02:00			`cat $< \| sed 's/vs10/vs$(MSVC_VER)/g' \| sed 's/VS10/VS$(MSVC_VER)/g' > $(top_builddir)/build/win32/vs$(MSVC_VER)/$@`

			`%.vcxproj:`
			`cat $(top_builddir)/build/win32/vs10/$@ \| sed 's/v100/v$(MSVC_VER)0/g' > $(top_builddir)/build/win32/vs$(MSVC_VER)/$@`

			`%.props:`
			`cat $(top_builddir)/build/win32/vs10/$@ \| sed 's/<VSVer>10<\/VSVer>/<VSVer>$(MSVC_VER)<\/VSVer>/g' > $(top_builddir)/build/win32/vs$(MSVC_VER)/$@`

			`%.vcxproj.filters:`
			`cp $(top_builddir)/build/win32/vs10/$@ $(top_builddir)/build/win32/vs$(MSVC_VER)/$@`
Add autotools scripts to create VS2012 projects As the project file format for Visual Studio 2012 is only slightly different from Visual Studio 2010 projects, we can provide support for building GLib (and other projects) with Visual Studio 2012 with relatively little effort. This might change when we eventually get GLib to work with the Windows 8 (Modern UI/formerly Metro) APIs, but this will suffice for the time being for people needing to build GLib with Visual Studio 2012. Basically all that needs to be done at 'make dist' is: -Copy the .sln/.props/README.txt/.vcxproj files and replace the VS2010 stuff with VS2012 stuff -Copy the .vcxproj.filters as is 2012-11-19 05:58:55 +01:00