| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
| |
Use gcov/lcov and coverage.py; merge all results and provide
the final html reports as job artifacts.
|
|
|
|
|
|
|
|
|
|
|
| |
The TEST_NAMES env var gets translated to work with the pytest syntax
(foo.py::class::method).
Rename one class which triggers a pytest warning because it starts with
"Test" but isn't one.
Remove erroring out on Python warnings as pytest triggers some
deprecation warnings by default.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gobject-introspection requires an import lib (.dll.a) on Windows,
so build that as well.
Disable the dbus tests until we have a temp bus like with autotools.
Unset MSYSTEM to disable the os.sep hackery.
This hit a bug in GI for the mingw+no-libtool case, see
https://bugzilla.gnome.org/show_bug.cgi?id=791902
The fix has been applied to MSYS2 in the meantime, see
https://github.com/Alexpux/MINGW-packages/pull/3308
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Takes the documentation developed at
https://github.com/pygobject/pygobject-docs
and puts into /docs
See https://pygobject.readthedocs.io for how it looks
Now that we move to gitlab we can use webhooks to trigger builds
on readthedocs from gitlab directly and we should also have a nicer
contribution UX.
This also gets rid of most of README/HACKING/INSTALL and moves most
of the information into the documentation. The README is kept short
and only makes clear what pygobject is and points to the online docs
as that should answer all questions.
setup.py now sets the content of README.rst as long_descriptions,
as that is the content shown on PyPI. This makes the page on PyPI
look the same as on gitlab.
https://bugzilla.gnome.org/show_bug.cgi?id=791448
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of wrapping autotools add a proper setuptools based build system.
Compared to the autotools one this does not install .pc files or headers
and does not allow running tests.
It uses pkg-config for discovering dependencies and explictely searches
for .pc files in the Python prefix so that pycairo installations in a
virtualenv are discovered. When using MSVC, pkg-config is skipped and
it is assumend that INCLUDE and LIB is properly set up.
Version information and requirements are parsed from configure.ac, package
metadata is parsed from PKG-INFO.in.
Also adds a "setup.py distcheck" command which makes sure all tracked files
end up in the tarball and that the tarball builds (no tests are run atm).
https://bugzilla.gnome.org/show_bug.cgi?id=789211
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
See https://wiki.gnome.org/Projects/GnomeCommon/Migration
Visible changes:
* --enable-compile-warnings is now [no/auto/yes] instead of
[no/minimum/yes/maximum/error]
* warnings are errors by default except for releases or if
--disable-Werror is passed (which is the default in jhbuild)
AX_APPEND_COMPILE_FLAGS() gets used to disable some warnings enabled by
AX_COMPILER_FLAGS() because they trigger with pycairo/python headers.
Tested with gcc 6.3, clang 3.8.1
https://bugzilla.gnome.org/show_bug.cgi?id=777713
|
|
|
|
|
|
|
|
|
|
| |
This commit adds a setup.py file which just calls the autotools to
configure/make/make install.
It is heavily inspired by the similar work from Simon McVittie on
dbus-python.
https://bugzilla.gnome.org/show_bug.cgi?id=767988
|
|
|
|
|
|
|
|
|
|
| |
Add a couple of demos demostrating the use of CSS, the css files are
stored into a GResource binary file compiled with glib-compile-resources,
the comments in gtk-demo.py explain the usage of GResource.
Signed-off-by: Simon Feltman <sfeltman@src.gnome.org>
https://bugzilla.gnome.org/show_bug.cgi?id=719722
|
|
|
|
|
|
|
|
| |
Based on notes in https://wiki.gnome.org/Valgrind we need to use
always-malloc for valgrind runs.
Add check.valgrindlog and check.valgrindxml which output valgrind logs into
an ignored local tmp. Output logs are named <head-sha>-$TEST_NAMES.log so we
can track commits and use diff tools on the logs.
|
|
|
|
|
|
|
| |
Use gnome-common's new code coverage flags. Default to enabling code coverage
in autogen.sh (but not for dist).
To use this, run "make check-code-coverage" after building.
|
| |
|
|
|
|
|
|
| |
- Ignore *.o, backup files, and generated Makefiles in all subdirectories
- Ignore *.pyc files.
- Do not ignore .gitignore, we actually want to track this.
|
|
|
|
|
| |
git.mk is a script maintained in pango. From time to time we must
check if it was updated and update it here.
|
|
|
|
|
|
| |
files to .gitignore
Signed-off-by: Dieter Verfaillie <dieterv@optionexplicit.be>
|
| |
|
| |
|
| |
|
|
|