| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
g-ir-scanner 'relocatable' at runtime."
It's a bit too soon for this one, misunderstood review on irc.
Apologies for the mess!
This reverts commit 0102c517c44d3e8fc3baf2394cb92281511941e3.
|
|
|
|
|
|
| |
'relocatable' at runtime.
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=625494
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=655437
|
|
|
|
|
| |
Generating Python source code is problematic for srcdir != builddir;
steal a the trick of putting global data in __builtins__ from jhbuild.
|
| |
|
|
|
|
|
| |
Separate "preparing" a release locally from actually uploading it,
and automate bumping the version in configure.ac.
|
| |
|
|
|
|
|
|
| |
Return a non-zero result when opening the output file fails and
don't use g_error() for other failures when writing out the file,
since such errors should not produce a core dump.
|
|
|
|
|
| |
This should better avoid them being exported. Rename
girepository-parser.la to girepository-internals.la for clarity.
|
|
|
|
|
| |
This is cleaner and faster, and prepares us better for an incoming
import of CMPH.
|
|
|
|
|
|
|
|
|
| |
Rather than introspecting the current directory, use the environment
variable we know is present if and only if we're running uninstalled.
This will be less prone to failure when we switch to nonrecursive
make, since the generated script will be in the top builddir, not
tools/ anymore.
|
| |
|
|
|
|
|
|
|
| |
For backwards compat, keep the presence of the environment
variable at all to mean "exception".
Also start a HACKING file.
|
|
|
|
|
| |
Keep a typedef for backwards compatibility, until
the major bindings has moved over.
|
|
|
|
|
| |
Useful when debugging build problems for both me, and potentially over
IRC.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We never actually include multiple modules in the compiler,
so just nuke that. Also rather than passing around GIrModule
consistently pass around a GIrTypelibBuild structure which
has various things.
This lets us maintain a stack there which we can walk for
better error messages.
Also, fix up the node lookup in giroffsets.c; previously
it didn't really handle includes correctly. We really need to
switch to always using Foo.Bar (i.e. GIName) names internally...
|
|
|
|
|
|
| |
It can't really work right now because we rely on dumping data at runtime,
which requires the library. If in the future we support static scanning,
we can reinvestigate embedded typelibs.
|
| |
|
|
|
|
|
|
|
|
| |
g_irepository_require
Take a GError * for typelib loading code, validate the header. This
fixes bizarre errors from gjs where g_irepository_require would happily
load old typelibs.
|
|
|
|
|
| |
Move out the girwriter out of generate.c. Still a private API,
but that will probably change in the future.
|
|
|
|
|
| |
Get rid of all globals in gir generator, in preparation for
moving all code into libgirepository
|
|
|
|
|
| |
Rename gtypelib.h -> gitypelib-internal.h and rename
gtypelib.c to gitypelib.c
|
|
|
|
|
| |
It's been broken for some time, remove it instead of letting
it bitrot.
|
|
|
|
| |
For GLib arrays, write out the array type to the tgir
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
People have wanted support for marking (out) on functions of the
form:
/**
* clutter_color_from_pixel:
* @pixel: A pixel
* @color: (out): Color to initialize with value of @pixel
*/
void
clutter_color_from_pixel (guint32 pixel, ClutterColor *color);
Where the caller is supposed to have allocated the argument; the
C function just initializes it. This patch adds support for this
argument passing style to introspection. In this case, we see the
(out), and notice that there's only a single indirection (*) on
the argument, and assume that this means (out caller-allocates).
https://bugzilla.gnome.org/show_bug.cgi?id=604749
|
|
|
|
|
|
|
|
| |
Foreign structs are special in the sense that there might
be native bindings (for instance PyCairo for PyGI) that provides
the same functionallity as the introspected variant.
https://bugzilla.gnome.org/show_bug.cgi?id=610357
|
| |
|
|
|
|
| |
Also suppress a bit more using @
|
|
|
|
|
|
| |
gir: embed <callback> inside <field>
typelib: if a field contains a callback, store it just after the FieldBlob
girepository API: no additions
|
|
|
|
|
| |
Looking for .git/.svn breaks in tarball scenarios; instead just see
if our source directory is named 'tools'.
|
|
|
|
| |
This lets us pick up non-default /usr/bin/python2.6 correctly.
|
| |
|
|
|
|
|
| |
This avoids having processes with the typelibs currently open exploding
immediately.
|
|
|
|
| |
Remove support for (scope object) as it lacks a real use case.
|
|
|
|
| |
and other make distcheck fixes.
|
|
|
|
|
|
|
| |
Parse the c:prefix from the .gir, include it in the header. Armed with this
information, we can now optimize lookups of GTypes because we
have the requirement that GTypes must start with the c:prefix. We do
fall back though if a lookup fails.
|
|
|
|
| |
This avoids issues with unexpanded variables, i.e. ${exec_prefix}/libdir
|
|
|
|
|
|
| |
We don't want to pollute the global namespace with our private
libraries. Also, this sidesteps all the craziness that is happening
with OS vendors changing how Python installs modules.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Broadly speaking, this change adds the concept of <vfunc> to the .gir.
The typelib already had most of the infrastructure for virtual functions,
though there is one API addition.
The scanner assumes that any class callback slot that doesn't match
a signal name is a virtual. In the .gir, we write out *both* the <method>
wrapper and a <vfunc>. If we can determine an association between
them (based on the names matching, or a new Virtual: annotation),
then we notate that in the .gir.
The typelib gains an association from the vfunc to the function, if
it exists. This will be useful for bindings since they already know
how to consume FunctionInfo.
|
|
|
|
|
|
|
|
| |
We now support an extensible mechanism where arbitrary key-value
pairs may be associated with almost all items, including objects,
methods, and properties.
These attributes appear in both the .gir and the .typelib.
|
|
|
|
|
|
|
|
|
| |
Add --all option, which is intended to show some information not
usually included in the GIR.
Currently, it shows the size of structs and unions.
Signed-off-by: Andreas Rottmann <a.rottmann@gmx.at>
|
|
|
|
|
|
|
|
| |
Similar to GObject class structs, we pair up GInterfaces with
their C structures.
Also, move some GLib-specific things into glibast.py, and make
the naming more generic.
|
|
|
|
|
| |
We keep track of the source filename for every symbol. This enables
us to later filter symbols based on that name.
|
| |
|
| |
|
|
|
|
|
| |
This option is for specifying inside the .gir what C header files should
be included by C consumers (as opposed to parsed by the scanner).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We need to reference the get_type() functions we are going to dlsym
or otherwise the linker may not include them in the introspection
binary.
giscanner/dumper.py: Accept a list of _get_type() functions
and write an array referencing them into the introspection
binary.
giscanner/glibtransformer.py: Break parsing into too stages -
the stage where we compute the _get_type() functions and the
stage where we invoke the introspection binary.
tools/g-ir-scanner: Pass _get_type() functions from the
scanner when creating the introspection binary.
http://bugzilla.gnome.org/show_bug.cgi?id=572075
|
|
|
|
|
| |
This was suggested during a refactoring of the affected code for
bug 567906.
|