| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Reported-and-tested-by: Dominique Leuenberger <dimstar@opensuse.org>
Signed-off-by: Igor Gnatenko <ignatenko@src.gnome.org>
Reviewed-by: Colin Walters <walters@verbum.org>
|
|
|
|
|
|
| |
Signed-off-by: Igor Gnatenko <ignatenko@src.gnome.org>
https://bugzilla.gnome.org/show_bug.cgi?id=769600
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Various distributions (mainly RPM based so far) make use of automatic
dependencies extracted from typelib files (they can require other typelibs
and also shared libraries)
Current features
* Print used shared libraries
* Print used typelib dependencies
Based-on-patch-by: Dominique Leuenberger <dimstar@opensuse.org>
Reference: https://bugzilla.gnome.org/show_bug.cgi?id=665672
Reviewed-by: Colin Walters <walters@verbum.org>
Signed-off-by: Dominique Leuenberger <dimstar@opensuse.org>
Signed-off-by: Igor Gnatenko <ignatenko@redhat.com>
|
|
|
|
|
|
|
|
|
| |
A condition was supposed to test if GI_SCANNER_DEBUG environment
variable is unset or empty, but instead always evaluated to true.
This results in any build pausing in pdb whenever an uncaught exception
occurs in a g-ir-* tool.
https://bugzilla.gnome.org/show_bug.cgi?id=757443
|
|
|
|
|
|
|
|
| |
The transition to Python 3.x compatibility accidentily removed the
'relocatability' support that was added, so re-enable this support on
Windows again.
https://bugzilla.gnome.org/show_bug.cgi?id=757126
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=744535
Signed-off-by: Garrett Regier <garrett.regier@riftio.com>
|
|
|
|
|
|
| |
Add conditional import for Python 3's renamed builtins module.
https://bugzilla.gnome.org/show_bug.cgi?id=679438
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add unicode_literals future import which turns any string literal
into a unicode string. Return unicode strings from the Python C extension
module. Force writing of annotations (g-ir-annotation-tool) to output utf8
encoded data to stdout.
This is an initial pass at following the "unicode sandwich"
model of programming (http://nedbatchelder.com/text/unipain.html)
needed for supporting Python 3.
https://bugzilla.gnome.org/show_bug.cgi?id=679438
|
|
|
|
|
|
|
| |
Use future import "print_function" and update relevant uses of print
as a function call. See: PEP 3105
https://bugzilla.gnome.org/show_bug.cgi?id=679438
|
|
|
|
|
|
|
|
|
|
| |
Import Python 3 compatible "true division" from the future (PEP 238).
This changes the Python 2 classic division which uses floor division
on integers to true division. Verfied we don't actually use the
division operator anywhere in the code base so this a safety for
supporting both Python 2 and 3.
https://bugzilla.gnome.org/show_bug.cgi?id=679438
|
|
|
|
|
|
| |
Use absolute_import to ensure Python 3 compatibility of the code base.
https://bugzilla.gnome.org/show_bug.cgi?id=679438
|
|
|
|
|
|
|
|
| |
Otherwise the error is "no input files" which is very confusing.
https://bugzilla.gnome.org/show_bug.cgi?id=753160
Signed-off-by: Ben Boeckel <mathstuf@gmail.com>
|
|
|
|
| |
... so it lives next to the rest of the maintainer utilities.
|
|
|
|
|
|
| |
g-ir-annotation-tool, g-ir-doc-tool and g-ir-scanner where identical
except for the module and function being invoked.
Avoid code duplication and generate these from a common template.
|
| |
|
|
|
|
|
|
| |
'relocatable' at runtime.
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
| |
|
|
|
|
|
|
| |
'relocatable' at runtime.
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
|
|
|
|
|
|
|
|
| |
The "--code" option was removed years ago in ac81f3e8c5f1c380d16677232d67466e739da283
so remove references to it from README and g-ir-compiler(1)
Remove the "--no-init" option from g-ir-compiler and g-ir-compiler(1)
as it was documented to "can only be used if --code is also specified",
so no reason to keep it around.
|
|
|
|
| |
And bump our GLib requirement.
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|