| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Use the HIGHENTROPYVA linker option on x64 builds with MSVC 2012 and
later to enhance the security of the built binaries.
Pointed out by Ignacio Casal Quinteiro.
|
|
|
|
|
| |
Let people know about the situation where one is able to build the
introspection files directly from within the Visual Studio projects.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds the introspection NMake Makefiles buildable from within the
Visual Studio projects, so that the whole Visual Studio build process
would be simplified. At its current state, this will build the
introspection files for PangoCairo and Pango, but does not include
PangoFT2 support, so this is not supported in the [Release|Debug]_FC
configs. For this to work, one needs to have a complete installation of
GObject-introspection in $(GlibEtcInstallRoot), and will need to ensure
that PythonDir (or PythonDirX64 on x64 systems) corresponds to the
same Python series that was used to build GObject-Introspection.
This needs to be built (and cleaned) separately as this is not built by
default, by building/cleaning the pango-introspect project directly.
In this commit, also rename the PythonPath entries in the projects and
property sheets, so that we avoid getting confused with the PYTHONPATH
envvar; and for Visual Studio 201x builds, we use Python 3.4.x by
default 2010, 2012 and 2013, and 3.6.x by default for 2015 and 2017, as
what is done now in GObject-Introspection projects.
|
|
|
|
|
|
|
|
|
| |
Some files that this script will process might have UTF-8 items in
there, which can cause problems on Python 3.x as it is more strict and
careful on unicode issues. Fix this by:
-Doing what we did before on Python 2.x
-Opening the file with encoding='utf-8' on Python 3.x
|
|
|
|
|
|
|
| |
This enables the new feature recently added in G-I where we can generate
the full NMake Makefile module to build the .gir files by passing in a list
of C includes, instead of needing to specify them fully one-by-one with
--c-include=...
|
|
|
|
|
| |
This enables one to build the introspection files using Visual Studio
2017.
|
|
|
|
|
| |
This will ensure that it will be up-to-date when
win32/vs10/pango-install.props is re-generated.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This updates the autotools scripts to support Visual Studio 2017 builds, by copying
the Visual Studio 2010 projects and updating items in there as necessary.
Note the format of the toolset version changed, so we allow one to specify a
custom toolset version string and hence use it if it is specified, otherwise
the toolset version string is generated as it was before.
Since Visual Studio 2017 aims to be compatible on the CRT level as Visual Studio
2015, the 2017-compiled binaries should be usable without problems with 2015-compiled
binaries.
|
|
|
|
|
| |
Some more paths in auxillary scripts and NMake Makefiles need to be
updated as well...
|
|
This allows one to go down one less level in the directory tree to get to the
Visual Studio project files, and so make things more in line with the rest of
the GTK+ stack. This also cleans up the Visual Studio 201x projects as there
are some items that can be actually combined.
|