luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-11-08 10:26:16 +01:00
Code Issues Packages Projects Releases Wiki Activity
fdd0ed1972
glib/build/Makefile-newvs.am

46 lines
2.1 KiB
Plaintext
Raw Normal View History

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
build/Makefile-newvs.am: Update Comments for Usage Update the notes that this is also used for Visual Studio 2015 support, and correct the MSVC_VER_LONG for MSVC 2015, which is 14, not 2015. Also add a note that this can be used for other projects that have Visual Studio build support.
2015-09-25 06:54:26 +02:00
# Create the Visual Studio 2012/2013/2015 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
build/Makefile-newvs.am: Update Comments for Usage Update the notes that this is also used for Visual Studio 2015 support, and correct the MSVC_VER_LONG for MSVC 2015, which is 14, not 2015. Also add a note that this can be used for other projects that have Visual Studio build support.
2015-09-25 06:54:26 +02:00
# This autotools file, from GLib, can be used in other projects
# that have Visual Studio build support, and is copied into
# $(srcroot)/build/.
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
build/Makefile-newvs.am: Update Comments for Usage Update the notes that this is also used for Visual Studio 2015 support, and correct the MSVC_VER_LONG for MSVC 2015, which is 14, not 2015. Also add a note that this can be used for other projects that have Visual Studio build support.
2015-09-25 06:54:26 +02:00
# MSVC_VER_LONG: Long Version of Visual Studio (2012, 2013, 14 and so on)
MSVC Builds: Prepare For Visual Studio 2015 Update the autotools module so that we can use it to upgrade the Visual Studio 2010 projects to become Visual Studio 2015-compatible. Note that this will make the MSVC 2015 builds use the the the latest VC140 CRT.
2015-09-07 08:46:10 +02:00
# MSVC_VER: Short Version of Visual Studio (11 for 2012, 12 for 2013, 14 for 2015 and so on)
# MSVC_FORMAT_VER: Use 12 for MSVC 2012 through 2015
%.sln:
sed 's/11\.00/$(MSVC_FORMAT_VER)\.00/g' < $(top_srcdir)/build/win32/vs10/$@ > $(top_builddir)/build/win32/vs$(MSVC_VER)/$@.tmp
sed 's/2010/$(MSVC_VER_LONG)/g' < $(top_builddir)/build/win32/vs$(MSVC_VER)/$@.tmp > $(top_builddir)/build/win32/vs$(MSVC_VER)/$@
rm $(top_builddir)/build/win32/vs$(MSVC_VER)/$@.tmp
%.txt:
sed 's/vs10/vs$(MSVC_VER)/g' < $(top_srcdir)/build/win32/vs10/$@ > $(top_builddir)/build/win32/vs$(MSVC_VER)/$@.tmp
sed 's/VS10/VS$(MSVC_VER)/g' < $(top_builddir)/build/win32/vs$(MSVC_VER)/$@.tmp > $(top_builddir)/build/win32/vs$(MSVC_VER)/$@
rm $(top_builddir)/build/win32/vs$(MSVC_VER)/$@.tmp
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
%.vcxproj:
Makefile-newvs: some .vcxproj.filters files are in builddir, some in srcdir Without this change, out-of-tree distcheck doesn't get very far. Similarly, allow *.vcxproj, *.props to be in either the builddir or the srcdir. Finally, since I'm touching these lines anyway, eliminate some useless uses of cat: "cat x | sed 's/foo/bar/' > y" is equivalent to "sed 's/foo/bar/' < x > y". Bug: https://bugzilla.gnome.org/show_bug.cgi?id=748176 Reviewed-by: Chun-wei Fan <fanchunwei@src.gnome.org>
2015-04-20 15:54:28 +02:00
if test -e $(top_srcdir)/build/win32/vs10/$@; then \
sed 's/v100/v$(MSVC_VER)0/g' < $(top_srcdir)/build/win32/vs10/$@ > $(top_builddir)/build/win32/vs$(MSVC_VER)/$@; \
build/Makefile-newvs.am: Fix %.vcxproj Rule The if-else statement added in commit 9bc3ae9 was missing a '\' after the 'else', causing 'make dist/distcheck' to break with "unexpected end-of-file" errors. Fix this-didn't notice this when reviewing that patch. My fault. :|
2015-04-22 10:36:13 +02:00
else \
Makefile-newvs: some .vcxproj.filters files are in builddir, some in srcdir Without this change, out-of-tree distcheck doesn't get very far. Similarly, allow *.vcxproj, *.props to be in either the builddir or the srcdir. Finally, since I'm touching these lines anyway, eliminate some useless uses of cat: "cat x | sed 's/foo/bar/' > y" is equivalent to "sed 's/foo/bar/' < x > y". Bug: https://bugzilla.gnome.org/show_bug.cgi?id=748176 Reviewed-by: Chun-wei Fan <fanchunwei@src.gnome.org>
2015-04-20 15:54:28 +02:00
sed 's/v100/v$(MSVC_VER)0/g' < $(top_builddir)/build/win32/vs10/$@ > $(top_builddir)/build/win32/vs$(MSVC_VER)/$@; \
fi
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
%.props:
Makefile-newvs: some .vcxproj.filters files are in builddir, some in srcdir Without this change, out-of-tree distcheck doesn't get very far. Similarly, allow *.vcxproj, *.props to be in either the builddir or the srcdir. Finally, since I'm touching these lines anyway, eliminate some useless uses of cat: "cat x | sed 's/foo/bar/' > y" is equivalent to "sed 's/foo/bar/' < x > y". Bug: https://bugzilla.gnome.org/show_bug.cgi?id=748176 Reviewed-by: Chun-wei Fan <fanchunwei@src.gnome.org>
2015-04-20 15:54:28 +02:00
if test -e $(top_srcdir)/build/win32/vs10/$@; then \
sed 's/<VSVer>10<\/VSVer>/<VSVer>$(MSVC_VER)<\/VSVer>/g' < $(top_srcdir)/build/win32/vs10/$@ > $(top_builddir)/build/win32/vs$(MSVC_VER)/$@; \
else \
sed 's/<VSVer>10<\/VSVer>/<VSVer>$(MSVC_VER)<\/VSVer>/g' < $(top_builddir)/build/win32/vs10/$@ > $(top_builddir)/build/win32/vs$(MSVC_VER)/$@; \
fi
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
%.vcxproj.filters:
Makefile-newvs: some .vcxproj.filters files are in builddir, some in srcdir Without this change, out-of-tree distcheck doesn't get very far. Similarly, allow *.vcxproj, *.props to be in either the builddir or the srcdir. Finally, since I'm touching these lines anyway, eliminate some useless uses of cat: "cat x | sed 's/foo/bar/' > y" is equivalent to "sed 's/foo/bar/' < x > y". Bug: https://bugzilla.gnome.org/show_bug.cgi?id=748176 Reviewed-by: Chun-wei Fan <fanchunwei@src.gnome.org>
2015-04-20 15:54:28 +02:00
if test -e $(top_srcdir)/build/win32/vs10/$@; then \
cp $(top_srcdir)/build/win32/vs10/$@ $(top_builddir)/build/win32/vs$(MSVC_VER)/$@; \
else \
cp $(top_builddir)/build/win32/vs10/$@ $(top_builddir)/build/win32/vs$(MSVC_VER)/$@; \
fi
Reference in New Issue Copy Permalink