| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Algorithm which detects whether argument type is pointer checks for
trailing '*' characters in c:type .gir elements. This failed if ctype
is either 'gpointer' or 'gconstpointer'. Add specific check for
gpointer/gconstpointer types when deducing pointerness of the type.
https://bugzilla.gnome.org/show_bug.cgi?id=658848
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This applies mainly to GValue, which is defined as:
struct _GValue
{
/*< private >*/
GType g_type;
/* public for GTypeValueTable methods */
union {
gint v_int;
guint v_uint;
glong v_long;
gulong v_ulong;
gint64 v_int64;
guint64 v_uint64;
gfloat v_float;
gdouble v_double;
gpointer v_pointer;
} data[2];
};
Previously, the scanner did not understand the array of unions. This
resulted in g_struct_info_get_size returning an incorrect size for
GValue (at least on 32bit systems).
Fix this by making up a separate union declaration for the GIR that can
be referenced by the array.
https://bugzilla.gnome.org/show_bug.cgi?id=657040
|
|
|
|
|
| |
For gjs we want to switch to using introspection data for signals, and
the "notify" signal being missing from GObject was a problem.
|
|
|
|
|
|
|
| |
Windows doesn't know about LPATH, but PATH is part
of it's .dll search order.
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
Some pkgconfig files contain these flags on Windows, for example
gtk+-3.0.pc has -mms-bitfields in it's Cflags. Nothing is done yet
with these though, we only accept these flags for now...
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
|
|
|
|
|
| |
... on Windows, so take care of the extension.
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
|
|
|
|
|
| |
... on Windows, as it uses gio-unix.
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
|
|
|
|
|
|
| |
... on Windows as it points to the MinGW installation directory,
which doesn't have any .gir files to start with anyway.
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
|
|
|
|
|
|
|
|
|
|
| |
Otherwise, we fail to properly locate the typelibs, because on Windows
the value of GOBJECT_INTROSPECTION_LIBDIR depends on where Glib has been
installed. Due to the nature of how we handle software that depends on
Glib on Windows (it is recommended that each program bundles it's private
copy), we're working in a "multi-prefixed" environment. Hence the value
computed at build time will most likely not even exist at runtime.
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
|
|
|
|
|
|
|
| |
Windows.
So only include it when WIN32 is not defined.
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
|
|
|
|
|
|
|
|
|
|
|
| |
line arguments.
This continues to reuse the LIBTOOL variable from automake if it's set,
but works around some MSYS weirdness: When running g-ir-scanner, MSYS
changes a command-line argument --libtool="/bin/sh ../../libtool" into
--libtool=c:/opt/msys/1.0/bin/libtool. So just use sh.exe without path
because we already "know" where the libtool configure produced is.
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
|
|
|
|
|
| |
By simply using -shrext ".pyd".
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
|
|
|
|
|
| |
Both when x$have_cairo_gobject = xyes and x$have_cairo = xyes.
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
|
|
|
|
|
| |
Without repeated output created by AC_MSG_CHECKING([for Win32])
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- AM_CHECK_PYTHON_HEADERS macro now allows PYTHON_INCLUDES to be overridden
from an environment variable and
- the new AM_CHECK_PYTHON_LIBS macro to check for ability to link against
libpython. This also allows PYTHON_LIBS and PYTHON_LIB_LOC to be overridden
from their respective environment variables.
This allows gobject-introspection to be built with MinGW/MSYS by doing:
PYTHON_DIR="/c/Python27"
SRC_DIR="/d/dev/gnome.org/checkout/gobject-introspection/src"
...
PYTHON_INCLUDES="-I${PYTHON_DIR}/include/" \
PYTHON_LIBS="-L${PYTHON_DIR}/libs/ -lpython${PYTHON_VERSION}" \
PYTHON_LIB_LOC="${PYTHON_DIR}/libs/" \
"${SRC_DIR}/configure" \
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
|
|
|
| |
It only applies to native binaries.
|
| |
|
|
|
|
|
|
| |
grealpath.h defines GetFullPathNameA() as windows.h is
not imported, but for gitscanner.c, windows.h is imported and the compiler
throws an error.
|
| |
|
| |
|
|
|
|
| |
Usage: ./_build/gi-dump-types g_object_get_type
|
|
|
|
| |
While we're here move config.h to the top for consistency.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=658075
|
|
|
|
| |
Regenerated from glib fe4fc3e8b5a5ad8d4113c4df1fe8e0e9f295035e
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=657686
|
| |
|
|
|
|
| |
The new missing-element-type warning triggers for these.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 81abc2eb63317003a11d1484e84698a37e8ec035 tries harder to keep
the c:type if it was overriden by a (type) annotation. However, the
_resolve() function was also called for (element-type), which had
undesirable effects - we'd copy the container c:type to the element
type.
Fix this by splitting out the c:type preservation to only happen when
processing toplevel types.
https://bugzilla.gnome.org/show_bug.cgi?id=656931
|
| |
|
|
|
|
|
|
| |
While looking for a different bug, I noticed that the introspectable
pass lists was missing GSList. And the warning was never set up
to fire anyways. Fix it and add a test.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
There were some cases of handling GObject and GInitiallyUnowned which
were not necessary. Removing special cases from them simplified code
and as a bonus it added 'GObject::notify' signal into GIR, which was
not there previously.
https://bugzilla.gnome.org/show_bug.cgi?id=657446
|
| |
|
| |
|
|
|
|
|
|
|
| |
This reverts commit 3553cd0a4631f1b57fb608e3f3f78a1a0cfd602a.
Turns out it was wrong, XID is 64 bit on a 64 bit system. Plus
the scanner doesn't like multiple level typedefs.
|
|
|
|
|
|
|
|
| |
XIDs are CARD32, which corresponds to guint32 on all platform, not
gulong (which is 64 bit on x86_64). Fix that, and use alias indirection
to more accurately reflect the typedefs.
https://bugzilla.gnome.org/show_bug.cgi?id=643620
|
|
|
|
|
| |
It's not needed as the project uses inline comments
for documentation.
|
| |
|
|
|
|
|
| |
Replace deprecated autoconf macros
Use new libtool syntax
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Complement fix for g-ir-scanner which converts every GdkRectangle
gtype to CairoRectangleInt. Make sure that C-side API is also aware
of this workaround.
Use case requiring this patch:
When binding implementation wants to get/set property, it can use either
GI-based approach (g_property_info_xxx() funcs), or just GLib facilities.
Although former is probably preferred, there are cases when latter is still
needed (e.g. gstreamer uses dynamic properties, which are not present in the
gir). In this case, binding implementation queries the type of the propertyb
(using g_object_class_find_property()), it gets GDK_TYPE_RECTANGLE,
and without the patch it cannot map it to any known type.
https://bugzilla.gnome.org/show_bug.cgi?id=655423
|