| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
They haven't been used in years and would need an update for meson.
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Rename the msvc readme file because otherwise gitlab picks it up as the default
one for some reason.
|
|\
| |
| |
| |
| | |
autotools: dist all meson files
See merge request GNOME/gobject-introspection!44
|
| | |
|
|/
|
|
|
|
|
|
|
|
| |
AUTHORS/CONTRIBUTORS haven't been updated in years and the info
is in git.
ChangeLog is in git as well.
Those files were there because automake by default (gnu flavour)
requires them, but we use the "foreign" flavour now.
|
|
|
|
|
|
| |
Let the people know how building GObject-Introspection on Visual Studio
using Meson is done, as the Visual Studio projects have been dropped in
favor of Meson.
|
|
|
|
|
|
|
|
|
|
| |
We now have Meson build files which can handle builds using Visual
Studio now, so we should focus maintenance efforts on the build system
for Visual Studio on Meson.
This will also allow build options to be more flexible, and has the
advantage of being able to build directly out of a GIT checkout, without
needing to generate source dist tarballs.
|
|
|
|
|
|
| |
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/.
|
|
|
|
|
| |
So if I patch things downstream I can more easily rebuild the
autotools.
|
| |
|
|
|
|
|
| |
Updated from:
https://raw.githubusercontent.com/jcrocholl/pep8/1.6.2/pep8.py
|
|
|
|
| |
... so it lives next to the rest of the maintainer utilities.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add Python unittest module parameterization support to gi-tester through the
use of a "TESTARGS" variable. Use the Automake test harness along with
gi-tester for running the Python annotationparser tests.
Add tests/scanner/annotationparser/Makefile.am and localize testing
rules and EXTRA_DIST setup to this file. Specific Python tests can now be
run as follows:
cd tests/scanner/annotationparser
make check TESTS=test_patterns.py TESTARGS=TestTagValueStability
https://bugzilla.gnome.org/show_bug.cgi?id=720713
|
|
|
|
|
|
|
|
| |
Switch both cmph-bdz-test and gthash_test to use the Automake test harness.
Use EXTRA_PROGRAMS and EXTRA_LTLIBRARIES along with CLEANUP to allow lazy
dependency evaluation of testing targets.
https://bugzilla.gnome.org/show_bug.cgi?id=720713
|
|
|
|
| |
no longer used since b2fd4f54883cd701a0c280655c93e20b04897ed2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Version in our tree is a wee bit outdated. For example,
later work will introduce an utf8 encoded python source
file which our old pep8.py does not yet understand (yeah,
it really was *that* ancient)...
Updated from:
https://raw.github.com/jcrocholl/pep8/1.4.5/pep8.py
Takes 552c1f1525e37a30376790151c1ba437776682c5,
f941537d1c0a40f0906490ed160db6c79af572d3,
5a4afe2a77d0ff7d9fea13dd93c3304a6ca993de and
a17f157e19bd6792c00321c8020dca5e5a281f45 into account...
https://bugzilla.gnome.org/show_bug.cgi?id=699535
|
|
|
|
|
|
|
|
|
|
| |
- Configure with --enable-doctool when running "make distcheck"
- Remove $(top_builddir)/.make-check-passed as the pre-commit hook
using this was removed in de84ea0cf212c251e099f456bb675492f664e93d
- Fix CLEANFILES + manual rm invocations
- Fix running warning tests uninstalled (VPATH build issue)
https://bugzilla.gnome.org/show_bug.cgi?id=697669
|
| |
|
|
|
|
|
|
| |
I'm sick and tired of this.
https://bugzilla.gnome.org/show_bug.cgi?id=693040
|
|
|
|
|
|
|
|
| |
Instead of telling the user to do so and failing, we can just install the hook
ourselves. This saves the user some trouble and more importantly avoids
breaking tests in jhbuild continuous integration setups.
https://bugzilla.gnome.org/show_bug.cgi?id=686388
|
|
|
|
|
|
|
| |
... to tests/scanner/annotationparser/test_patterns.py because the
following patch will remove giscanner/annotationpatters.py
https://bugzilla.gnome.org/show_bug.cgi?id=688897
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The tests in giscanner/annotationpatters.py only test the regular
expression programs used when parsing GTK-Doc comment blocks but
do not test the structure of the resulting "parse tree".
This patch adds 193 GTK-Doc comment blocks and the expected
results AnnotationParser should return (with it's current level
of understanding of GTK-Doc comment block syntax). These are
compared by tests/scanner/annotationparser/test_parser.py which
complains with a diff on failure.
https://bugzilla.gnome.org/show_bug.cgi?id=688897
|
|
|
|
|
|
|
|
|
| |
-Add Makefile-msvcproj.am to fill in the cmph, girepository and
g-ir-compiler projects
-Add various Makefile.am's under build/ to distribute the
Visual C++-related files.
https://bugzilla.gnome.org/show_bug.cgi?id=681820
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=672254
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Replace deprecated autoconf macros
Use new libtool syntax
|
| |
|
| |
|
| |
|
|
|
|
| |
This is where install-module lives now.
|
|
|
|
| |
So they get updated when configure changes.
|
|
|
|
|
| |
Separate "preparing" a release locally from actually uploading it,
and automate bumping the version in configure.ac.
|
| |
|
|
|
|
| |
This is a list of test programs to run under "gtester".
|
|
|
|
|
| |
This is cleaner and faster, and prepares us better for an incoming
import of CMPH.
|
|
|
|
|
| |
It has false positives difficult to work around now, and is
really better run as a periodic check anyways.
|
|
|
|
|
| |
I don't have a GPG key setup anymore, not interested in
the archaeology to find it right now.
|
| |
|
|
|
|
|
| |
If .git is not present, do not require the pre-commit
hook to be present either
|
| |
|
| |
|
|
|
|
|
| |
It's been broken for some time, remove it instead of letting
it bitrot.
|
|
|
|
|
|
|
| |
This should make sure that new tarballs contain the reference
documentation.
https://bugzilla.gnome.org/show_bug.cgi?id=618651
|
|
|
|
| |
Also, make sure that it is included in the dist
|
|
|
|
|
| |
This will make it easier for third-party projects to use
introspection by having easy make rules.
|
|
|
|
|
| |
It's better to keep lawyers happy if we ship the actual license
files rather than just mentioning them in COPYING.
|