| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
...when we use the distutils that is packaged with SetupTools instead of the
one that comes with Python stdlib, which is often the case on newer Python 3.9+
(or so) installations. Calling distutils.ccompiler.new_compiler() in this
case won't work when running on Visual Studio builds, and we use the
compiler instance for distutils's customize_compiler(), which was never
meant for Visual Studio. So, we do nothing in customize_compiler() if we are
not using a unix compiler type.
This will fix the warn-* tests for G-I on Python 3.9.x or later when the default
distutils used is now the one that comes with setuptools, without needing to
use the envvar SETUPTOOLS_USE_DISTUTILS=stdlib.
|
|
|
|
|
|
| |
This allows to perform more introspection tests in gjs and other
implementations when it comes to set/get fields or "cast" an union
member to the main union type
|
|
|
|
|
|
|
| |
Such kind of arrays can be easily be allocated as we know the size of
each array element.
See: https://gitlab.gnome.org/GNOME/gjs/-/merge_requests/806
|
|
|
|
| |
This is based on f64f88baaeaca277687e6231b3cea6d14a26996b
|
|
|
|
| |
This is based on 201c920cbd0b816f4e19b52c1b28746935fdcb00.
|
|
|
|
| |
Based on 86430a27d26b9b72b02ff0b81eeaa5df0525646c.
|
| |
|
| |
|
|
|
|
| |
Fixes clang builds
|
| |
|
| |
|
|
|
|
| |
GLib commit: 2.74.0
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
generated C file
When g-ir-scanner is used by another project, than that project might
have the GLIB_VERSION_* macros defined. This is useful to ensure that
only intended glib API is used.
The project might then also pass the CFLAGS to g-ir-scanner, without
filtering those defines out. This can lead to compiler warnings.
For example, NetworkManager sets the version macros to GLIB_VERSION_2_40
and thus gets these warnings
/NetworkManager/tmp-introspect66917zc4/NM-1.0.c: In function ‘dump_object_type’:
/NetworkManager/tmp-introspect66917zc4/NM-1.0.c:252:13: warning: Not available before 2.70
252 | if (G_TYPE_IS_FINAL (type))
| ^~~~~~~~~~~~~~~~~
/NetworkManager/tmp-introspect66917zc4/NM-1.0.c: In function ‘dump_fundamental_type’:
/NetworkManager/tmp-introspect66917zc4/NM-1.0.c:370:13: warning: Not available before 2.70
370 | if (G_TYPE_IS_FINAL (type))
| ^~~~~~~~~~~~~~~~~
But these warnings are not correct. The installed g-ir-scanner knows for which
glib version to generate code. Undefine the macros to avoid the warning.
|
|
|
|
| |
GLib commit: 2.73.3-44-g66c4e35e2
|
|
|
|
|
| |
GLib has been requiring a C99 toolchain for a while, now. It makes no
sense to have gobject-introspection depend on C89.
|
| |
|
|
|
|
|
|
| |
This helps with gtk!4965.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
|
|
|
|
|
|
| |
https://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html
Based on https://github.com/katef/kgt/blob/c9d8ad246855c6b65e42371be7898f4073c28d18/examples/c99-grammar.iso-ebnf#L247-L252
|
|
|
|
|
| |
The test returns a newly allocated GValue, so it should not be marked
transfer none.
|
|
|
|
|
|
| |
This parameter may not be NULL even if the function described by the
GIFunctionInfo has a void return type, so we should not say this in the
documentation.
|
| |
|
|
|
|
| |
The toolchain is different enough to warrant its own CI job imo.
|
|
|
|
|
| |
cmph is vendored and other one is bison/flex generated code.
Not much we can do here, so disable those warnings there.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The existing code tries to mirror how the linker finds DLLs by
searching for the import libs and then looking for the matching
shared lib name.
While llvm has a dlltool clone it doesn't provide the --identify
option to extract the shared lib name. Instead we use the fact that
llvm import libs include the dll name in the archive member name, so
we can use "nm" there to get the same result.
To decide which strategy to use we run dlltool and check if it contains
"llvm-dlltool" in the output.
This fixes the .gir and .typelib files containing bogus values for the
shared library names when building with clang + mingw-w64 on Windows.
I'm not quite sure if the libtool part is actually needed there,
but I left it in to keep the diff small.
|
|
|
|
|
|
|
| |
While gcc on Windows allows being passed -rpath and just ignores it,
llvm/lld will fail with "lld: error: unknown argument: -rpath".
There is no such thing as rpath on Windows, so just skip it.
|
| |
|
| |
|
|
|
|
| |
We require Meson 0.60, to match newer GLib.
|
|
|
|
| |
The `check` argument to `run_command()` is now mandatory.
|
|
|
|
|
|
| |
- Install pcre2, as it's a new GLib dependency.
- Do not use CFLAGS to inject -Werror
- Use idiomatic Meson subcommands
|
|
|
|
|
| |
GLib 2.58 has long since been released. We should always match GLib's
version, since we update the introspection data regularly.
|
|
|
|
| |
Rebased up to 2.73.2.
|
|
|
|
| |
Based on https://gitlab.gnome.org/GNOME/glib/-/commit/113d7263
|
|
|
|
|
|
|
| |
This 10 line gir file was good enough for the past
12 years, but now I want to have pango api with FcConfig
arguments appear in the docs, and the way to that leads
through the gir nowadays.
|
|
|
|
| |
We need to unblock the CI pipeline, in order to fix them.
|
|
|
|
| |
The original one was so old Meson didn't recognise it as a wrap file.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Fedora 34 is EOL, and by the time we release GNOME 43, Fedora 35 will be
close to EOL too.
|
| |
|
|
|
|
| |
GLib bumped its own dependency to Meson 0.60.
|
| |
|
| |
|
|
|
|
| |
This is based on 0c6a1af9d616e110b4610d5a6a992d02ed1a5c21
|
|
|
|
|
| |
In glib-print.c example, make the error message refer to the same function
(GLib.assertion_message) as the code.
|
|
|
|
|
|
|
|
|
| |
Projects like pango depending on fontconfig-2.0.gir or
any other gir provided by gobject-introspection in its
sources directory need to have these gir's available
in the build directory, where the rest of generated
girs are created so they are found when using
gobject-introspection dependency.
|