| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This was broken with the last commit to remove a lot of the special
hacks to link to girepository in the dumper.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Imports gtk-doc comment from gio. In the future comments
should go into the gio sources instead of here, wer're we will
use the annotation-tool to update the extracted sources.
|
| |
|
|
|
|
|
|
|
| |
Add 'transfer mode' annotations for GAction, GActionGroup, GAppInfo,
GApplication and GAsyncInitable
https://bugzilla.gnome.org/show_bug.cgi?id=629790
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=629708
|
| |
|
| |
|
|
|
|
| |
Add annotations fixing warnings in in GVolume and GVolumeMonitor
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Add some more (transfer full) annotations left out in commit cd0de25.
|
|
|
|
|
| |
Add (transfer full) and (array zero-terminated=1) to various GLib
and Gio functions.
|
|
|
|
|
| |
This enables glib documentation to be added to the generated gir using the original source
eg. --with-glib-src=/usr/src/glib
|
| |
|
|
|
|
| |
It has been broken for a while and nobody uses it.
|
|
|
|
|
| |
Add namespacing prefixes to the static .gir files. Support the empty
prefix, as is needed for xlib.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
One of the first big changes in this rewrite is changing the Type
object to have separate target_fundamental and target_giname properties,
rather than just being strings. Previously in the scanner, it was
awful because we used heuristics around strings.
The ast.py is refactored so that not everything is a Node - that
was a rather useless abstraction. Now, only things which can have
a GIName are Node. E.g. Type and Field are no longer Node.
More things were merged from glibast.py into ast.py, since it isn't
a very useful split.
transformer.py gains more intelligence and will e.g. turn GLib.List
into a List() object earlier. The namespace processing is a lot
cleaner now; since we parse the included .girs, we know the C
prefix for each namespace, and have functions to parse both
C type names (GtkFooBar) and symbols gtk_foo_bar into their
symbols cleanly. Type resolution is much, much saner because
we know Type(target_giname=Gtk.Foo) maps to the namespace Gtk.
glibtransformer.py now just handles the XML processing from the dump,
and a few miscellaneous things.
The major heavy lifting now lives in primarytransformer.py, which
is a combination of most of annotationparser.py and half of
glibtransformer.py.
annotationparser.py now literally just parses annotations; it's
no longer in the business of e.g. guessing transfer too.
finaltransformer.py is a new file which does post-analysis for
"introspectability" mainly.
girparser.c is fixed for some introspectable=0 processing.
|
|
|
|
|
|
|
|
|
| |
Rather than have the scanner/parser handle both e.g. "glong" and
"long", simply use the GLib types everywhere.
This commit adds TYPE_LONG_LONG and TYPE_LONG_DOUBLE to the
scanner types; however, rather than add them to the typelib,
they're just marked as not-introspectable.
|
|
|
|
|
|
|
| |
This makes type parsing more uniform.
Delete the typedef for GSList in foo.h - that's not
supported anymore, or at least for now.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GIMarshallingTests will be replaced with automatically
generated code; it was far from comprehensive, and was a pain
to maintain.
The namespacing in Everything was broken; it had an empty C
prefix effectively, because all the symbols just started with
"test". We do want "test" as part of the symbols, since otherwise
the exported API would be weird. Fix this by changing the namespace
to Regress (i.e. prefixing all the C code with Regress). This
makes sense anyways because Everything wasn't really Everything.
We no longer install a pre-built regress.(so,gir,typelib); instead we
install the C code to
$(datadir)/gobject-introspection/tests/regress.[ch].
Bindings should compile this.
|
|
|
|
| |
This new variable maps to --pkg-export.
|
| |
|
| |
|
|
|
|
|
|
|
| |
These used to live in gir-repository; similarly to how we're presently just holding
random .gir files for the lowlevel bits of the platform, suck these in.
In the future they'll be obsoleted by foreigns.
|
|
|
|
|
| |
It isn't going to be fully introspectable anytime soon; we'd need a crap-ton
of (skip).
|
|
|
|
| |
It's obsoleted by the introspectable=0 handling.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
To make the tests pass again
|
|
|
|
|
|
| |
These may conflict.
https://bugzilla.gnome.org/show_bug.cgi?id=624191
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously we had both e.g. GI_TYPE_TAG_LONG and GI_TYPE_TAG_INT64,
but in fact the typelib is already machine-specific, so it makes sense
to just encode this as a fixed type. The .gir remains abstract.
We also remove size_t from the typelib; one would never want to treat
it differently than an integer.
time_t is removed as well; while bindings like gjs had special handling
to turn it into e.g. a JS Date object, I don't think we should encourage
people to use these POSIX types in their API. Use GTimeVal or the like
instead.
Because the typelib is now really machine-specific, we need to remove
the -expected.tgirs from git. (We could potentially add a check
which wasn't just a literal diff later)
https://bugzilla.gnome.org/show_bug.cgi?id=623774
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds support for instantiable fundamental object types,
which are not GObject based. This is mostly interesting for being
able to support GstMiniObject's which are extensivly used in GStreamer.
Includes a big test case to the Everything module (inspired by
GstMiniObject) which should be used by language bindings who wishes to
test this functionallity.
This patch increases the size of the typelib and breaks compatibility
with older typelibs.
https://bugzilla.gnome.org/show_bug.cgi?id=568913
|
|
|
|
|
|
|
|
|
| |
Moving to <doc> allows us to better preserve whitespace. XML has no
facility for whitespace-preserving attributes.
Second, for arrays and lists, both types with unknown element_type can
occur in the current scanner; it's least wrong if we write out an
<any> type.
|
| |
|
| |
|