| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
This tests that after installing the g-i tools a simple project using
them can be build with meson and autotools.
Fixes #341
|
|
|
|
| |
powershell instead of cmd, win2016 instead of 2012r2
|
|
|
|
|
|
| |
This reverts commit d01a387475e2665275a6cd6b0059bf91121b8300.
The nightly run time does not have Meson 0.54
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When gobject-introspection-1.0 pkg-config is not found on the system,
Meson can fallback to configure g-i as subproject and needs a dependency
object to replace the pc file.
The dependency file needs to ensure that typelibs are created before
compiling any other gir and provide the girdir for files within build
directory. It also need to provide glib dependencies required to compile
girs.
Bump Meson version to 0.54.0 to use meson.override_dependency().
|
|
|
|
|
|
|
| |
In our case we have to do various special things in case glib isn't available
through pkg-config and not all tests are run.
Add a CI job that tests this case so we don't regress.
|
|
|
|
| |
See !186
|
|
|
|
|
| |
The different dir separator seems to confuse meson now
(likely a new change in mingw Python path handling..)
|
|
|
|
|
|
|
| |
Similar to !180 this should prevent devs from not running all tests by
accident.
This also adds some checks for the required doctool dependencies, mako and markdown.
|
|
|
|
|
|
|
|
|
| |
We require cairo only to run all tests and thus default it to false.
This usually results in developers not using it when working on changes and
tests depending on cairo then failing in CI.
This changes it to a feature option that defaults to auto, so that devs that
have cairo headers installed will automatically use it.
|
|
|
|
|
| |
It's what we use for testing in CI (so not even sure older versions work) and
glib master now also depends on this 0.49.
|
| |
|
| |
|
| |
|
|
|
|
| |
To unbreak continuous
|
| |
|
| |
|
|
|
|
|
| |
The cairo dependency fallback code is copied from pygobject. I assume that
will work for msvc users (cairo is disabled by default anyway)
|
|
|
|
|
| |
The headerid extension no longer exists in 3.x. Use the toc extension instead.
The toc_depth option was only added in 3.x so still try headerid first.
|
|
|
|
|
| |
Add a simple test using the docwriter so we trigger the docwriter related
Python imports.
|
|
|
|
|
| |
Getting rid of autotools wont be easy, so make sure we run all tests on Windows,
not just the ones ported to meson.
|
| |
|
|
|
|
|
|
| |
glib did the same thing this cycle, see
https://gitlab.gnome.org/GNOME/glib/merge_requests/196
for details
|
|
|
|
|
| |
GLib, a wrapped dependency, requires 0.48.0, so our CI environments should
have that installed.
|
|
|
|
|
|
|
|
| |
doctool is an auto option and was disabled by the recent addition of
a new dependency on the markdown Python module. Since we didn't have that
in our testing docker image the tests were just skipped.
This makes sure we error out if any dependencies are missing again.
|
|
|
|
|
| |
This prints the error count to stderr, and more importantly 0 when
everything is OK so we know it did something.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
g-i includes an old version of pep8 and pyflakes and uses that
during "make check".
It (1) doesn't catch all cases newer versions of pycodestyle/pyflakes catch
and (2) doesn't test all Python files (3) doesn't work with meson.
Instead of updating just remove them and depend on flake8 instead.
To run the checks simply run flake8 in the root dir.
This also makes it possible to run those checks when using meson and
not autotools.
To not get test suite failures on flake8 updates move the checks from
"make check" to an extra "make check.quality" target.
|
|
|
|
|
|
|
|
|
| |
* This adds a new dependency on autoconf-archive.
* Pass WARN_CFLAGS/WARN_LDFLAGS/WARN_SCANNERFLAGS to everything we control the source of
* Disables all warning flags which make the build error out for now, we'll re-enable them
in followup commits.
* AX_COMPILER_FLAGS is used with the release flag always on so we don't get
-Werror by default.
|
|
|
|
| |
it seems to be working again now
|
| |
|
|
|
|
|
|
| |
Switch to docker hub for now as the gitlab registry is broken.
Disable the glib version check in configure.ac because we don't
strictly need it for testing.
|
|
|
|
|
|
|
|
| |
This allows us to build with Python 2 and run tests with it.
This requires the new "python" meson module which was added in 0.46.0 so
bump the required meson version (glib needs a newer one anyway).
Also fixes a small test error under Python 2.
|
| |
|
|
|
|
|
|
| |
Since GI master most times depends on an unstable glib release we
need to pull it in as a subproject anyway. Not installing a system glib
makes sure we don't depend on it by accident.
|
| |
|
| |
|
|
|
|
| |
glib now requires 0.46.1 and GI uses it as a subproject in CI
|
|
|
|
|
|
| |
We should use the GitLab registry, to allow everyone with the
appropriate credentials for gitlab.gnome.org to push images for
CI.
|
|
|
|
| |
We sadly need redhat-rpm-config because of Python's distutils.
|
|
|
|
|
| |
The base Fedora image we use for CI doesn't always have the version of
Meson we depend on; let's use Python's pip to install Meson, instead.
|
|
|
|
|
| |
Use the Fedora build dependencies for the gobject-introspection package
as a source.
|
|
|
|
|
| |
If we end up building GLib as a subproject, we're going to need all the
GLib dependencies.
|
|
|
|
|
| |
We need Git in order to check out the subprojects, in case the
dependencies do not match with the system ones.
|
|
Based on the GLib and GTK equivalent CI environment, with a Docker
container used to run the build.
|