AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity
84ff404a17
gtk2/build/Makefile-newvs.am

54 lines
2.3 KiB
Plaintext
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
# 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 04:54:26 +00:00
# Create the Visual Studio 2012/2013/2015 project files
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
# from the Visual Studio 2010 project files
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 04:54:26 +00:00
# This autotools file, from GLib, can be used in other projects
# that have Visual Studio build support, and is copied into
# $(srcroot)/build/.
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
# Author: Fan, Chun-wei
# November 05, 2012
Visual Studio builds: Support Visual Studio 2017 Update the autotools scripts so that we can support Visual Studio 2017 by copying the 2010 projects and updating items as needed to obtain the 2017 projects. Note that since the toolset version string changed for Visual Studio 2017, so allow the use of a custom toolset version string, otherwise just generate the toolset version string as we did before. Also, note that Visual Studio 2017 aims to be compatible with 2015 on the CRT level, so there should not be any problems using 2017-compiled binaries with 2015-compiled ones.
2017-02-17 07:06:25 +00:00
# MSVC_VER_LONG: Long Version of target Visual Studio (2012, 2013, 14 and so on)
# MSVC_VER: Short Version of target Visual Studio (110 for 2012, 120 for 2013, 140 for 2015, 141 for 2017)
# MSVC_TOOLSET: Use if target MSVC toolsett is not in the form v $(MSVC_VER)0, meaning v$(MSVC_TOOLSET)
if MSVC_BASE_NO_TOOLSET_SET
MSVC_BASE_TOOLSET = $(MSVC_BASE_VER)0
endif
if MSVC_NO_TOOLSET_SET
MSVC_TOOLSET = $(MSVC_VER)0
endif
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
%.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 05:59:28 +00: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 13:54:28 +00:00
if test -e $(top_srcdir)/build/win32/vs10/$@; then \
Visual Studio builds: Support Visual Studio 2017 Update the autotools scripts so that we can support Visual Studio 2017 by copying the 2010 projects and updating items as needed to obtain the 2017 projects. Note that since the toolset version string changed for Visual Studio 2017, so allow the use of a custom toolset version string, otherwise just generate the toolset version string as we did before. Also, note that Visual Studio 2017 aims to be compatible with 2015 on the CRT level, so there should not be any problems using 2017-compiled binaries with 2015-compiled ones.
2017-02-17 07:06:25 +00:00
sed 's/v100/v$(MSVC_TOOLSET)/g' < $(top_srcdir)/build/win32/vs10/$@ > $(top_builddir)/build/win32/vs$(MSVC_VER)/$@; \
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 13:54:28 +00:00
else \
Visual Studio builds: Support Visual Studio 2017 Update the autotools scripts so that we can support Visual Studio 2017 by copying the 2010 projects and updating items as needed to obtain the 2017 projects. Note that since the toolset version string changed for Visual Studio 2017, so allow the use of a custom toolset version string, otherwise just generate the toolset version string as we did before. Also, note that Visual Studio 2017 aims to be compatible with 2015 on the CRT level, so there should not be any problems using 2017-compiled binaries with 2015-compiled ones.
2017-02-17 07:06:25 +00:00
sed 's/v100/v$(MSVC_TOOLSET)/g' < $(top_builddir)/build/win32/vs10/$@ > $(top_builddir)/build/win32/vs$(MSVC_VER)/$@; \
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 13:54:28 +00:00
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 05:59:28 +00:00
build/: Force MSVC project file generation on Makefile.am changes Make the Makefile.am targets for generating the Visual Studio projects re-generate the project files and the header listings whenever the Makefile.am's that include build/Makefile.msvcproj changes, so that whenever a source/header is added, they will be reflected in the projects and in the property sheets that are used to copy the headers. Also ensure that these are applied to the vs11, vs12 and vs14 projects when this happens, as they are copied and processed from the Visual Studio 2010 projects.
2016-10-19 06:48:08 +00:00
%.props: $(top_builddir)/build/win32/vs10/Makefile
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 13:54:28 +00: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 05:59:28 +00: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 13:54:28 +00: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