| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
The main development branch of GObject Introspection is now called
"main", following the change in GLib and GTK.
|
|
|
|
|
|
|
|
|
|
| |
Because of skepticism I received in #224, I made this PR which keeps the
testsuite and CI improvements but doesn't add any new build options. I
hope this would be less controversial:
- no new knobs
- tests for those using existing build options
- CI tests `build_introspection_data = false`
|
|
|
|
|
| |
Let people know how building G-I and running g-ir-scanner with clang-cl and
friends is being supported, as this support is now added.
|
|
|
|
|
| |
Let the people know how _giscanner.pyd handles looking up for dependent DLLs
on Python 3.8.x or later on Windows.
|
|
|
|
|
|
|
| |
It appears that tests/repository/gitypelibtest.c needs to be added to
the list of files that we must change the optimization flag from /O2 to
/O1 in order that the Visual Studio 2008 x64 compiler does not hang, due
to compiler optimization issues.
|
|
|
|
| |
This is what https://wiki.gnome.org/Initiatives/GnomeGoals/MesonPorting suggests.
|
|
|
|
|
|
| |
Let people know the common pitfalls when building and using the Python
scripts when building, to avoid confusions on the Python installation
that is used to run the Python scripts.
|
|
|
|
|
|
| |
The default Cairo-GObject DLL filename should be for MinGW/mingw-w64
builds, not Visual Studio builds, hence the likely need to use the
-Dcairo-libname option for MSVC builds... doh.
|
|
|
|
|
| |
Mention about the configuration options cairo-libname and python as they
are likely necessary for G-I to be built and used successfully.
|
|
Rename the msvc readme file because otherwise gitlab picks it up as the default
one for some reason.
|