| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
Fix sandbox violation using subproject variables
added in https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2465
Use global source and build root directories
|
|
|
|
|
|
|
|
|
| |
We attempted to return a value in void-return-type functions in both
gicallableinfo.c and gitypeinfo.c, so avoid that since that will trigger a
C4098 warning on Visual Studio, which is considered an error if we are building
against an installed version of GLib 2.68.x or later.
This will fix builds against GLib-2.68.x and later on Visual Studio.
|
|
|
|
|
|
| |
This fixes support for macros like `g_message()` in GLib.
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
|
|
|
|
|
|
|
| |
This fixes support for macros like `G_BREAKPOINT()` or `G_DEBUG_HERE()`
in GLib.
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
|
| |
|
| |
|
|
|
|
| |
GLib 2.72.0 is now out.
|
|
|
|
|
|
|
|
|
| |
It seems that optparse might just ignore storing options without a
default. In this case, the `--compiler` option should be initialised to
`None`, but instead it just gets ignored.
Without the `hasattr()` check, updating the introspection data for GLib
fails with a Python backtrace.
|
|
|
|
| |
This is based on f61187428eaff51b5aae121df1615e02117ef44f.
|
|
|
|
|
| |
We don't use Autotools, and we don't generate files inside the source
directory any more.
|
|
|
|
|
| |
The main development branch of GObject Introspection is now called
"main", following the change in GLib and GTK.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds gi_type_tag_argument_from_hash_pointer() and
gi_type_tag_hash_pointer_from_argument(). They do the same thing as
the corresponding g_type_info_... functions, which are used to pack and
unpack the correct field of a GIArgument into/from a data pointer in
GHashTable or GList, regardless of machine architecture or endianness.
These functions take a GITypeTag obtained from
g_type_info_get_storage_type(), instead of a GITypeInfo pointer. (The
storage type is the only piece of data that is actually used from the
GITypeInfo structure.)
It's intended for bindings using an argument cache, such as GJS and
PyGObject, so that they don't have to store a whole 64-bit GITypeInfo
pointer in their cache in many common cases, and can just store the 5-bit
type tag instead.
The original g_type_info_... functions are reimplemented in
terms of the new g_type_tag... functions.
|
| |
|
| |
|
|
|
|
|
| |
We need it for close(), especially when unistd.h is not available, such as in
the case of Visual Studio-style builds.
|
|
|
|
|
|
|
|
| |
We can just update the for loop condition to be >0 for all builds, which
is actually equivilant to >=1 as we are essentially comparing an
unsigned 32-bit int, so that we don't need to worry about fixing the
VS2012 bug invasively, as Visual Studio 2012 x64 is more sensitive about
sizes of variables (e.g. pointer sizes in this case)
|
|
|
|
|
|
|
|
|
|
|
| |
The __ia64 and __x86_64__ macros are defined for GCC but not Visual
Studio, but actually this code path should also be taken for Visual
Studio when doing a 64-bit build (x86_64/x64 and aarch64/arm64, _WIN64
will be defined for these cases), since Windows is an LLP64 platform.
This will avoid C4311/C4312 warnings on Visual Studio builds, which are
often warnings of concern as we are dealing with pointers with differing
sizes on 32-bit and 64-bit Windows builds.
|
|
|
|
|
|
|
|
|
| |
Later GLib versions assume that warning C4715 is an error as we want ot
be sure that functions that return a value do indeed return one by all
means.
Avoid this warning by adding a 'return 0' in brz_search_packed(), it
might be pointless but does indeed avoid the warning.
|