| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Coerce input temporarily inside xmlwriter into Unicode to do
string manipulation, and then only convert it to "UTF8str" when
writing into the data buffer.
|
|
|
|
|
|
| |
The assumption is that the only allowed source encoding
is utf-8. Always strings as unicode and fix up the transformer
and xml writer to properly output utf-8.
|
|
|
|
|
|
|
| |
g_strcompress() only does some of what we need; fork it
and add support for \x escapes too.
https://bugzilla.gnome.org/show_bug.cgi?id=595773
|
|
|
|
|
|
|
|
| |
These are the only things for which we expect native values to be
preserved; for e.g. flags and integers, we expect bindings to convert.
The particular rationale for this patch is to avoid flagging flags (sic)
as (out caller-allocates).
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This should better avoid them being exported. Rename
girepository-parser.la to girepository-internals.la for clarity.
|
|
|
|
|
|
| |
It seems in some cases (Debian libtool) we get an injected rpath
first for the jhbuild root, which screws us over since we need
the libraries from .libs.
|
| |
|
|
|
|
|
|
| |
The commit to use the c_symbol_prefix works in every case, except for
gdk_window_object_get_type(), which screws us. Fall back to the old
heuristic in this case.
|
|
|
|
| |
With nonrecursive they're in $(top_builddir) now
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
If we have a C symbol prefix for the target type, then use that to
identify methods that should be paired with it. The C symbol prefix
is derived from the name of the _get_type() function, so it's likely
that this is also the prefix given to methods for the type.
https://bugzilla.gnome.org/show_bug.cgi?id=634153
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=633227
|
|
|
|
|
|
|
| |
Some API such as gtk_text_iter_get_char returns an individual
"gunichar"; we should support this.
https://bugzilla.gnome.org/show_bug.cgi?id=633197
|
|
|
|
|
| |
On Debian, libtool won't pull in dependencies from internal libraries when
linking.
|
|
|
|
|
|
|
| |
This matches g_object_info_find_method, and allows us to add indexing
later.
https://bugzilla.gnome.org/show_bug.cgi?id=633204
|
|
|
|
|
| |
Because of Makefile.introspection, the .typelibs are still put in
gir/.
|
|
|
|
| |
girepository only explicitly deps on GObject, so this is correct.
|
|
|
|
|
|
|
|
|
|
|
| |
The previous commit aea515709 broke scanning for libraries not
in the current directory, such as scanning Gio from gobject-introspection.
In this case, it's wrong to add -L., and to move the other -L behind
the library. Instead, we should just do a "normal" link using
pkg-config --libs with few games.
https://bugzilla.gnome.org/show_bug.cgi?id=632701
|
|
|
|
|
| |
We need the typelib compiler to be built before we try to
build typelibs for the static gir files.
|
| |
|
|
|
|
| |
..but we still should be looking for pre-written girs in gir/.
|
|
|
|
|
| |
Since we're nonrecursive, the build artifacts live in $(top_builddir),
so look there now for files like Gio-2.0.gir.
|
|
|
|
|
| |
Otherwise it's really easy to unintentionally export unwanted symbols,
as would happen with the upcoming CMPH import.
|
|
|
|
|
|
| |
This is needed by the offsets code, and is generally useful. We
need to export it for a future patch which won't export symbols
with a leading _.
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
os.path.join barfs if we're passing it 0 arguments, as would happen
when doing "import foo".
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The C compiler will pick an enumeration type that accomodates the specified
values for the enumeration, so ignoring 64-bit enumerations, we can
have enumeration values from MININT32 to MAXUINT32. To handle this properly:
- Use gint64 for holding eumeration values when scanning
- Add a 'unsigned_value' bit to ValueBlob so we can distinguish the
int32 vs. uint32 cases in the typelib
- Change the return value of g_value_info_get_value() to gint64.
https://bugzilla.gnome.org/show_bug.cgi?id=629704
|
|
|
|
|
|
|
|
|
|
| |
Previously we just were sloppy and didn't bother to accurately compute
signed/unsigned for enumeration types. But since we expect bindings
to decode a field value or function return value from an integer to
an enumeration they have know whether an integer value is
0xffffffff or -1, so we need to do the full computation.
https://bugzilla.gnome.org/show_bug.cgi?id=629704
|
|
|
|
| |
This is a preparatory patch for adding a new basic tag.
|
|
|
|
|
|
| |
Otherwise people may not know about --warn-all.
https://bugzilla.gnome.org/show_bug.cgi?id=631644
|
| |
|
|
|
|
|
| |
The compiler path explicitly split()s the variable, we should do
so in the linker path too.
|
|
|
|
|
|
|
| |
Commit f97cc8687469f25752f79275 broke the lookup in
g_irepository_get_info; the passed offset is 0-based, then
we convert it to 1-based (and then back to 0 later...which needs
to be fixed).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before, we were adding the --libs-only-L from pkg-config files
during initial scanning, as if --library-path was specified,
*and* inside the dumper, we used --libs.
Fix this by always doing -L. <introspected libraries> <pkg-config libs>
This should ensure we don't duplicate the search path anyways.
https://bugzilla.gnome.org/show_bug.cgi?id=631348
|
|
|
|
|
|
| |
Might as well be liberal here, as long as we have a test case.
https://bugzilla.gnome.org/show_bug.cgi?id=631690
|
|
|
|
|
|
|
|
|
|
|
| |
This is a cleanup patch in preparation for future indexing
patches.
The lookup code was a mess trying to mash in the 3 different
cases of name, GType, and index into one mega-function.
Split it up properly, and move the core typelib internal-scanning
bits into gitypelib.c where it belongs.
|
| |
|
|
|
|
|
|
| |
Previously we bombed out if the minor version didn't match what
we expected; this was silly since the whole point of the minor
version is to enumerate compatible changes.
|
|
|
|
|
| |
...by default. However, the GI_SCANNER_DEBUG=save-temps option
helps for debugging.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
OS vendors which compile from the part-binary "tarballs" which
include e.g. pregenerated gtk-doc, they typically don't pass
--enable-gtk-doc. So conditionalizing "make install"
for docs on ENABLE_GTK_DOC won't work.
This is the same as GTK+ and other projects currently work.
|
|
|
|
|
| |
I don't have a GPG key setup anymore, not interested in
the archaeology to find it right now.
|