| 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.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
The .lib file was not copied from the right place, fix that.
|
| |
|
|
|
|
|
|
| |
We can't just use -llibxml2 for the libraries that libxml2 will link to,
as that will result in xml2.lib being searched rather than libxml2.lib
that we need, as the --msvc-syntax flag will eliminate the lib prefix for
the libraries. Instead, just pass in libxml2.lib explicitly to work around
this.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
This module is not used in G-I itself, but is copied and used in other
modules, so make sure paths in here are up-to-date after the project moved
to win32/ from build/win32
|
| |
|
|
|
|
|
| |
This is a follow-up commit to Evan Nemerson's addition to Makefile.introspection
so that we can pass in a number of C includes so that we make generate the
full NMake Makefile module with the command line to call g-ir-scanner in a
simpler and cleaner way.
|
| |
|
|
|
|
| |
Sync this file from GLib so that we can support Visual Studio 2017,
which is needed for the NMake Makefiles that are used to build the
introspection to work (which, are called from the project files).
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
... 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.
|
|
|
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/.
|
