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
58ecc57ca7
glib/win32/vs11/Makefile.am

49 lines
1.2 KiB
Makefile
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
EXTRA_DIST = \
README.txt \
glib.sln \
glib.vcxproj \
glib.vcxproj.filters \
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.vcxproj \
gobject.vcxproj.filters \
gthread.vcxproj \
gthread.vcxproj.filters \
gio.vcxproj \
gio.vcxproj.filters \
glib-compile-schemas.vcxproj \
glib-compile-schemas.vcxproj.filters \
gsettings.vcxproj \
gsettings.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 \
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
gresource.vcxproj \
gresource.vcxproj.filters \
Add MSVC Projects for Utility Programs Build and "install" the gio-querymodules and gdbus utility programs so that the Visual Studio builds of GLib is more comprehensive. The Python scripts for the GDBus codegen will be added to "installation" later.
2013-06-20 09:48:32 +02:00
gio-querymodules.vcxproj \
gio-querymodules.vcxproj.filters \
gdbus.vcxproj \
gdbus.vcxproj.filters \
MSVC Builds: Update vs11|vs12/Makefile.am The rename of install.vxproj to glib-install.vcxproj needs to be applied here as well for dist'ing the project files correctly.
2015-02-02 07:16:18 +01:00
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 \
MSVC 2010 Project Files: Split up the Property Sheets Like the Visual Studio 2008 project files, split up the property sheets so to ease maintenace, and to prepare to use autotools to fill in the header entries to "install". Put some of the items that are frequently repeated in the projects as well, also to simplify maintenance. Also, update the autotools files to automate the upgrade of Visual Studio 2010 project as we now have multiple property sheets to copy and process.
2013-08-21 10:57:11 +02:00
glib-build-defines.props \
glib-install.props \
glib-version-paths.props \
MSVC 2012 Projects: Rename a Property Sheet Forgot to update the property sheet file name from the Visual Studio 2010 update... Sorry!
2014-01-02 02:54:18 +01:00
glib-gen-srcs.props
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
Fix distcheck
2012-12-18 01:14:22 +01:00
DISTCLEANFILES = $(EXTRA_DIST)
Visual Studio builds: Fix previous commit Pushed the wrong version of the patch, sorry!
2017-02-15 07:14:05 +01:00
MSVC_BASE_VER = 10
build/Makefile-newvs.am: Do not hardcode the baseline MSVC version This is to allow specification of the baseline Visual Studio 201x version as the baseline version may not be 2010 anymore as we begin to require C99 features that will require Visual Studio 2013 or later.
2016-10-26 06:57:42 +02:00
MSVC_BASE_VER_LONG = 2010
Visual Studio builds: Fix previous commit Pushed the wrong version of the patch, sorry!
2017-02-15 07:14:05 +01:00
MSVC_VER = 11
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_VER_LONG = 2012
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
include $(top_srcdir)/win32/Makefile-newvs.am
Reference in New Issue Copy Permalink