| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
GLib 2.72.0 is now out.
|
|
|
|
| |
This is based on f61187428eaff51b5aae121df1615e02117ef44f.
|
|
|
|
| |
This is based on f9c08308ea0c25977b4e0153e868cb0a8703b75e
|
|
|
|
| |
This is based on c7031164b13d1e184aeaf5850a10897b06269735
|
|
|
|
| |
This is based on 0ea10bf904e2098739fe0f5df52be549343effa9
|
|
|
|
| |
This is based on d41282f7a85b0e1be61505ae85125a977a8ac557
|
| |
|
|
|
|
|
|
|
| |
GLib 2.70 has just been released, so let's sync up the documentation and
annotations.
Fixes: #402
|
| |
|
|
|
|
| |
Up to the 2.69.1 tag.
|
|
|
|
|
|
| |
Make the variable names intelligible, and include a bunch of built files
that are necessary to ensure that the generated GIR data actually
matches the GLib API.
|
|
|
|
|
|
|
|
|
|
| |
Because of skepticism I received in #224, I made this PR which keeps the
testsuite and CI improvements but doesn't add any new build options. I
hope this would be less controversial:
- no new knobs
- tests for those using existing build options
- CI tests `build_introspection_data = false`
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
meson inserts the dependency if the compiler is used directly, but
fails to do so if the compiler is run through a wrapper. This leads
to build race errors between building the compiler and using it.
Fix provided by Quentin Schulz <quentin.schulz@streamunlimited.com>
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
The old name used "host" according to Yocto's definition, but not
Meson's. The new name works for everyone.
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Actually, we shouldn't really need this. We are building `native: false`
binaries so when we look up a `native: true` binary the override should
not apply. I've fixed this upstream in meson in
https://github.com/NixOS/nixpkgs/pull/86080, though some backwards
compatibility migration might be in order.
In the meantime, we can make `gi_cross_use_host_gi` prevent the
overrides from happening, which will achieve the desired behavior.
Finally, this allows us to use `find_program` in `scanner_command`,
unconditionally, letting the presence of the override dictate whether a
freshly-built or pre-built `g-ir-scanner` is used.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Newer meson warns that option names can't start with "cross_", so
we have to prefix them:
"Option uses prefix "cross_", which is reserved for Meson. This will become an error in the future."
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This avoids compilation erroring out on C4819 (Unicode handling issue in the
Visual Studio compiler), notably when running on Chinese, Japanese and Korean
(CJK) locales.
This also applies -utf-8 into the cflags passed into the various g-ir-scanner
command lines that are used to generate the *.gir files, where -utf-8 is
available, so that we don't get flooded with C4819 warnings during the
build, and therefore avoid potential mishaps, as C4819 is a real warning that
warngs us the code may be incorrectly built.
|
| |
|
|
|
|
|
|
|
|
|
| |
See here:
https://gitlab.gnome.org/GNOME/gobject-introspection/merge_requests/64
Particularly, options are renamed to make it more readable and clear.
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
introspection-data and pkgconfig-sysroot-path options
With the first option, gobject-introspection tools (g-ir-doc-tool and g-ir-scanner)
that are already installed in the host system will be used for building the source tree.
With the second option, g-ir-scanner will be instructed to use an executable
wrapper to run binaries it's producing, and g-ir-compiler will be run
through the same wrapper (host system's g-ir-compiler cannot be used because
it's producing architecture-specific output).
With the third option, giscanner will be instructed to use a special ldd
command instead of system's ldd (which does not work when the binary to inspect
is compiled for a different architecture).
With the fourth option, it is possible to disable building of introspection data
(.gir and .typelib files), which may be difficult or impossible in cross-compilation
environments, because of lack of emulation (or native hardware) for the target architecture
on which the target binaries can be run.
With the fifth option, paths returned by pkg-config are prefixed with the sysroot
path (which is the destination path for cross-compiled items on the system where
cross-compilation happens).
These options are useful when cross-compiling for a different target architecture.
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Closes: https://gitlab.gnome.org/GNOME/gobject-introspection/issues/300.
|
| |
|
| |
|
| |
|