| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
acts as a regression test on the recognizing-GLib.List-inside-glib
part of the previous patch.
https://bugzilla.gnome.org/show_bug.cgi?id=602512
|
|
|
|
|
|
|
|
| |
Various places that check hardcoded type names were not always handling
the case of the type being used from within its own library (in which
case it won't have a type prefix). Make them more consistent.
https://bugzilla.gnome.org/show_bug.cgi?id=602512
|
|
|
|
|
|
| |
Only set "throws" in the latter case
https://bugzilla.gnome.org/show_bug.cgi?id=602512
|
| |
|
|
|
|
|
|
| |
Makes sure we can parse empty tags such as '@foo:' without
adding a : in the end which the typelib compiler will complain
about
|
| |
|
|
|
|
|
|
| |
By printing the function when arguments are missing
https://bugzilla.gnome.org/show_bug.cgi?id=604161
|
| |
|
|
|
|
| |
This is similar to a Clutter function.
|
|
|
|
| |
When looking up GINames, we should look in _names.names.
|
| |
|
|
|
|
|
| |
Keep track of the current line (the first 2000 chars of it) and include that in
syntax error messages. Also print that failed token in the error message.
|
|
|
|
| |
Increment linenumber in parse_comment which reads over multiline comments.
|
|
|
|
|
| |
Telling file and line would be better, but alreday this way one atleast has a
chance to fix it actually.
|
| |
|
|
|
|
|
|
|
|
| |
This is required as external projects such as gjs
are now using girffi and thus need the ffi cflags
to be able to link.
https://bugzilla.gnome.org/show_bug.cgi?id=603653
|
|
|
|
|
| |
This reverts commit 92abbe78dd7ffe0ff6d61db5f2bff0745a69115a and
494c1c92520917999407832453c11c2247b4e7bb.
|
| |
|
| |
|
|
|
|
|
| |
It's no longer necessary as the scanner figures out these
by itself
|
|
|
|
|
| |
This should have been included with f74823. Fixes
the async/notified scope annotation for glib/gio.
|
| |
|
|
|
|
|
|
|
| |
We use it for girffi.h. Remove the code to detect libffi without the .pc
file. If you don't have it, get it.
https://bugzilla.gnome.org/show_bug.cgi?id=603653
|
|
|
|
|
| |
Correctly guard with g_thread_supported, call g_thread_init before
g_type_init.
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=596960
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=602762
|
|
|
|
| |
Bug #602087.
|
|
|
|
|
|
|
|
| |
Due to a missing header, gobject-introspection fails to compile on OpenBSD.
And only due to headers-including-headers practice this doesn't blow up on
many other platforms.
https://bugzilla.gnome.org/show_bug.cgi?id=596226
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=603157
|
|
|
|
|
|
|
|
| |
GAsyncReadyCallback should have use the async scope per
default and GDestroyNotify should be notified if the
previous parameters are a callback and user data.
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=602862
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=603526
|
|
|
|
|
|
| |
want offset counting to be correct in its sublasses
https://bugzilla.gnome.org/show_bug.cgi?id=603038
|
|
|
|
|
|
|
|
| |
Previously it only worked for toplevel nodes. Now it works for any
node except <field>, since skipping a field would cause the
description of the struct layout to be wrong.
https://bugzilla.gnome.org/show_bug.cgi?id=602652
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=602672
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=597677
|
|
|
|
| |
Add g_base_info_equal.
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=557383
|
|
|
|
|
|
| |
gir: embed <callback> inside <field>
typelib: if a field contains a callback, store it just after the FieldBlob
girepository API: no additions
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Calling _resolve_param_type on a string instead of Node is fairly unusual,
and (as far as I could see) basically only happened in the Array processing
code. We were passing None as the ctype in this case, but we might as well
try using the name as a ctype too.
This fixes using GCallback (and in general any item in an array that comes
from an included gir).
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=599327
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=599327
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the case where a known class derives from a hidden one, we want
to use the most-derived parent class, rather than simply falling back
to GObject.
Example:
ShellEmbedWidget in gnome-shell derives from ClutterGLXTexturePixmap from clutter,
which is a hidden class. ClutterGLXTexturePixmap's parent itself is
ClutterX11TexturePixmap, which is also hidden. But its parent is
ClutterTexture, which we do know. Use that.
https://bugzilla.gnome.org/show_bug.cgi?id=598993
|
|
|
|
|
|
|
|
|
|
|
| |
Previously we were taking this in order from the dumper, which ends up
being some undefined order from GObject. Just use Node's cmp to sort
them by name explicitly.
This probably doesn't cover all possible instances of this problem,
but these fixes are right.
https://bugzilla.gnome.org/show_bug.cgi?id=597724
|
|
|
|
|
|
|
|
| |
When building the list of valid filenames for the scanner, resolve symlinks in
the filenames; the lexer does this when including files, so otherwise we'll get
filename mismatches if the path to the files being scanned includes a symlink.
Signed-off-by: Colin Walters <walters@verbum.org>
|
| |
|
| |
|