luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-11-11 03:46:17 +01:00
Code Issues Packages Projects Releases Wiki Activity
79e73da2e5
glib/win32/vs10/Makefile.am

69 lines
2.0 KiB
Makefile
Raw Normal View History

Cleanup and Enhance the MSVC Project Generation Make use of the common autotools module that is used to generate the MSVC project files from their respective templates so that the main build files beccome cleaner, and enhance them in a way that the headers that should be installed can be written to the property sheets during 'make dist', so that the chances of missing headers for MSVC builds can be greatly reduced. Also use this autotools module to fill in the projects for glib-compile-schemas and glib-compile-resources. https://bugzilla.gnome.org/show_bug.cgi?id=735429
2015-09-03 09:19:48 +02:00
GENERATED_ITEMS = \
glib.vcxproj \
glib.vcxproj.filters \
gobject.vcxproj \
gobject.vcxproj.filters \
gio.vcxproj \
gio.vcxproj.filters \
glib-compile-schemas.vcxproj \
glib-compile-schemas.vcxproj.filters \
glib-compile-resources.vcxproj \
glib-compile-resources.vcxproj.filters \
Visual Studio builds: Build the gio tool https://bugzilla.gnome.org/show_bug.cgi?id=768357
2016-07-04 06:43:36 +02:00
gio-tool.vcxproj \
gio-tool.vcxproj.filters \
Visual Studio builds: Move @GLIB_VERSION@ usage ... from glib-gen-srcs.[vsprops|props].in to glib-version-paths.[vsprops|props].in, and instead let autotools generate glib-version-paths.[vsprops|props] rather than glib-gen-srcs.[vsprops|props], as this will need to be referenced for other items as well, namely generating the .pc files which will become useful for introspection builds.
2016-02-25 11:37:01 +01:00
glib-version-paths.props \
Cleanup and Enhance the MSVC Project Generation Make use of the common autotools module that is used to generate the MSVC project files from their respective templates so that the main build files beccome cleaner, and enhance them in a way that the headers that should be installed can be written to the property sheets during 'make dist', so that the chances of missing headers for MSVC builds can be greatly reduced. Also use this autotools module to fill in the projects for glib-compile-schemas and glib-compile-resources. https://bugzilla.gnome.org/show_bug.cgi?id=735429
2015-09-03 09:19:48 +02:00
glib-install.props
build/win32: Make "Install" Property Sheet Generation More Robust List the files that are generated in the process to generate the glib-install property sheets, so that we can use that list as a depedency, as well as deleting those files in one shot after the property sheet is generated, so we don't need to worry about those in 'make distclean' or so.
2015-09-23 10:12:50 +02:00
MSVC10_HEADERS_LIST = glib.vs10.headers gobject.vs10.headers gio.vs10.headers
Visual C++ 2010 Project Files These are the actual GLib VS2010 project files (*.vcxproj, *.vcxproj.filters) and property sheet file (*.props) that are used to compile the GLib, GModule, GObject, GThread, GIO DLLs, along with the gspawn-win32-helper* programs, glib-genmarshal utility and testglib test program. A readme.txt file is also enclosed for references for building GLib under VS2010. Note that the project files for GLib, GIO and GObject are templates that makes use of the autotools items of my last commit so that maintenance of those files are simplified as new source files are added to these rather frequently. Suggestions are welcome for these-please let me know via BugZilla. Thank you!
2011-02-22 13:08:36 +01:00
EXTRA_DIST = \
Cleanup and Enhance the MSVC Project Generation Make use of the common autotools module that is used to generate the MSVC project files from their respective templates so that the main build files beccome cleaner, and enhance them in a way that the headers that should be installed can be written to the property sheets during 'make dist', so that the chances of missing headers for MSVC builds can be greatly reduced. Also use this autotools module to fill in the projects for glib-compile-schemas and glib-compile-resources. https://bugzilla.gnome.org/show_bug.cgi?id=735429
2015-09-03 09:19:48 +02:00
README.txt \
glib.sln \
glib.vcxprojin \
glib.vcxproj.filtersin \
glib-genmarshal.vcxproj \
glib-genmarshal.vcxproj.filters \
gspawn-win32-helper-console.vcxproj \
gspawn-win32-helper-console.vcxproj.filters \
gspawn-win32-helper.vcxproj \
gspawn-win32-helper.vcxproj.filters \
gmodule.vcxproj \
gmodule.vcxproj.filters \
gobject.vcxprojin \
gobject.vcxproj.filtersin \
gthread.vcxproj \
gthread.vcxproj.filters \
gio.vcxprojin \
gio.vcxproj.filtersin \
glib-compile-schemas.vcxprojin \
glib-compile-schemas.vcxproj.filtersin \
gsettings.vcxproj \
gsettings.vcxproj.filters \
glib-compile-resources.vcxprojin \
glib-compile-resources.vcxproj.filtersin \
Visual Studio builds: Build the gio tool https://bugzilla.gnome.org/show_bug.cgi?id=768357
2016-07-04 06:43:36 +02:00
gio-tool.vcxprojin \
gio-tool.vcxproj.filtersin \
Cleanup and Enhance the MSVC Project Generation Make use of the common autotools module that is used to generate the MSVC project files from their respective templates so that the main build files beccome cleaner, and enhance them in a way that the headers that should be installed can be written to the property sheets during 'make dist', so that the chances of missing headers for MSVC builds can be greatly reduced. Also use this autotools module to fill in the projects for glib-compile-schemas and glib-compile-resources. https://bugzilla.gnome.org/show_bug.cgi?id=735429
2015-09-03 09:19:48 +02:00
gresource.vcxproj \
gresource.vcxproj.filters \
gio-querymodules.vcxproj \
gio-querymodules.vcxproj.filters \
gdbus.vcxproj \
gdbus.vcxproj.filters \
glib-install.vcxproj \
MSVC builds: Add scripts to generate .pc files Add a generic script, pc_base.py, which can be utilized to obtain path info, along with user-input version info, which can be used to generate pkg-config .pc files. Also enhance replace.py a bit so that it can also be used in the future to replace multiple items in a file in one shot. This is done to make building introspection files easier, as it depends much on the pkg-config .pc files to work. Update the project files so that when Python is available, we can generate the full, usable .pc files when we complete and 'install' the builds, and copy them to appropriate locations so that pkg-config can be set to find them easily.
2016-03-10 13:33:35 +01:00
glib-install.vcxproj.filters \
Visual Studio builds: Move @GLIB_VERSION@ usage ... from glib-gen-srcs.[vsprops|props].in to glib-version-paths.[vsprops|props].in, and instead let autotools generate glib-version-paths.[vsprops|props] rather than glib-gen-srcs.[vsprops|props], as this will need to be referenced for other items as well, namely generating the .pc files which will become useful for introspection builds.
2016-02-25 11:37:01 +01:00
glib-build-defines.props \
Cleanup and Enhance the MSVC Project Generation Make use of the common autotools module that is used to generate the MSVC project files from their respective templates so that the main build files beccome cleaner, and enhance them in a way that the headers that should be installed can be written to the property sheets during 'make dist', so that the chances of missing headers for MSVC builds can be greatly reduced. Also use this autotools module to fill in the projects for glib-compile-schemas and glib-compile-resources. https://bugzilla.gnome.org/show_bug.cgi?id=735429
2015-09-03 09:19:48 +02:00
glib-install.propsin \
Visual Studio builds: Move @GLIB_VERSION@ usage ... from glib-gen-srcs.[vsprops|props].in to glib-version-paths.[vsprops|props].in, and instead let autotools generate glib-version-paths.[vsprops|props] rather than glib-gen-srcs.[vsprops|props], as this will need to be referenced for other items as well, namely generating the .pc files which will become useful for introspection builds.
2016-02-25 11:37:01 +01:00
glib-version-paths.props.in \
glib-gen-srcs.props \
Cleanup and Enhance the MSVC Project Generation Make use of the common autotools module that is used to generate the MSVC project files from their respective templates so that the main build files beccome cleaner, and enhance them in a way that the headers that should be installed can be written to the property sheets during 'make dist', so that the chances of missing headers for MSVC builds can be greatly reduced. Also use this autotools module to fill in the projects for glib-compile-schemas and glib-compile-resources. https://bugzilla.gnome.org/show_bug.cgi?id=735429
2015-09-03 09:19:48 +02:00
$(GENERATED_ITEMS)
Visual Studio builds: Move project files to win32/ It was suggested that the project files be moved here as we don't actually need to go two directory layers from $(srcroot), and would help us to standardize on things in the future across the board.
2017-01-09 07:00:46 +01:00
glib-install.props: $(top_srcdir)/win32/vs10/glib-install.propsin $(MSVC10_HEADERS_LIST)
-$(RM) $(top_builddir)/win32/vs11/glib-install.props
-$(RM) $(top_builddir)/win32/vs12/glib-install.props
-$(RM) $(top_builddir)/win32/vs14/glib-install.props
Visual Studio builds: Add support for Visual Studio 2017 This adds support for Visual Studio 2017 by updating the autotools files for copying and updating the Visual Studio 2010 project files. Since the toolset version of Visual Studio 2017 is no longer in the form of $(MSVC_VER_SHORT)0, we need to specify the full number, but this is a rather simple change we have here. Note that Visual Studio 2017's CRT aims to be compatible with the 2015's CRT, so it should be possible to use 2017-compiled code with the 2015-compiled ones.
2017-02-15 03:32:30 +01:00
-$(RM) $(top_builddir)/win32/vs15/glib-install.props
Visual Studio builds: Move project files to win32/ It was suggested that the project files be moved here as we don't actually need to go two directory layers from $(srcroot), and would help us to standardize on things in the future across the board.
2017-01-09 07:00:46 +01:00
$(CPP) -P - <$(top_srcdir)/win32/vs10/glib-install.propsin >$@
build/win32: Make "Install" Property Sheet Generation More Robust List the files that are generated in the process to generate the glib-install property sheets, so that we can use that list as a depedency, as well as deleting those files in one shot after the property sheet is generated, so we don't need to worry about those in 'make distclean' or so.
2015-09-23 10:12:50 +02:00
rm $(MSVC10_HEADERS_LIST)
Cleanup and Enhance the MSVC Project Generation Make use of the common autotools module that is used to generate the MSVC project files from their respective templates so that the main build files beccome cleaner, and enhance them in a way that the headers that should be installed can be written to the property sheets during 'make dist', so that the chances of missing headers for MSVC builds can be greatly reduced. Also use this autotools module to fill in the projects for glib-compile-schemas and glib-compile-resources. https://bugzilla.gnome.org/show_bug.cgi?id=735429
2015-09-03 09:19:48 +02:00
DISTCLEANFILES = $(GENERATED_ITEMS)
Reference in New Issue Copy Permalink