delta/gobject-introspection.git - gitlab.gnome.org: GNOME/gobject-introspection.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	build: Only generate .pc files for this package for MSVC builds	Chun-wei Fan	2017-09-01	1	-6/+1
\| \| \| \| \| \| \| \| \|	As we will be moving towards a manual find-header/find-library approach to find FreeType2, Cairo and libxml2 for Meson builds of GNOME packages that use them on Visual Studio, don't generate these generic versions as we should examine the .lib's that we find to see whether we have the functionality that is needed in the MSVC builds, instead of crafting pkg-config files for them.
*	MSVC 201x builds: Allow different Python versions per toolset	Chun-wei Fan	2017-07-12	1	-1/+5
\| \| \| \| \| \| \| \| \| \|	Use conditionals to select the Python installation, so that we can more stick to the default Visual Studio versions used to compile each official Python releases more closely. This means by default: -2010/2012/2013 builds use Python 3.4.x, which is built with 2010 -2015/2017 builds use Python 3.6.x, which is built with 2015
*	Visual Studio builds: Use the Centricular fork of libffi	Chun-wei Fan	2017-06-14	4	-22/+18
\| \| \| \| \| \| \| \| \|	The upstream libffi is getting bit-rotten on the regards of Windows/MSVC builds, and we are eventually moving towards to the Meson build system, so make use of the Centricular fork of libffi[1] which is better maintained and tested for Windows/MSVC builds. [1]: https://github.com/centricular/libffi
*	Visual Studio 201x builds: Fix "installation"	Chun-wei Fan	2017-04-18	1	-1/+1
\| \| \| \|	The .lib file was not copied from the right place, fix that.
*	MSVC builds: "Install" test sources like autotools builds	Chun-wei Fan	2017-02-20	1	-0/+12
\| \| \| \| \| \| \| \| \|	This makes sure that all the test sources that the autotools builds install are "installed" by the Visual Studio builds as well. For doing this, move the generation of everything.[c\|h] to gi-introspection-msvc.mak as we need to generate them for all builds, not just during building the tests.
*	Visual Studio builds: Support Visual Studio 2017	Chun-wei Fan	2017-02-15	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \| \| \|	... in the projects for now, the NMake Makefiles for the introspection files (.gir/.typelib) need to be updated as well, but that needs to be done a bit later. This is done by updating the autotools scripts, so that the Visual Studio 2010 projects are copied and the items are updated as necessary. Note that since the format of the platform toolset changed for Visual Studio 2017, a custom platform toolset string is allowed and used if specified, otherwise the platform toolset string is generated as it was before.
*	Visual Studio builds: Move build files to win32/	Chun-wei Fan	2017-01-09	27	-0/+2461
	As suggested, we don't really need two layers of directories to get to the projects, so move the project files to be under win32/ rather than build/win32/.