From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] glib: update to 2.80.0.
Date: Fri, 22 Mar 2024 09:03:35 +0100 [thread overview]
Message-ID: <20240322080335.0A75C22105@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49446@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2327 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/49446#issuecomment-2014537106
Comment:
I ported over the gobject-introspection qemuwrapper and patches and tested it with:
```
diff --git a/common/build-helper/meson.sh b/common/build-helper/meson.sh
index 6232f9260c2..e4e7171f031 100644
--- a/common/build-helper/meson.sh
+++ b/common/build-helper/meson.sh
@@ -67,8 +67,8 @@ cat > "${XBPS_WRAPPERDIR}/meson/xbps_meson.cross" <<-EOF
pkgconfig = '${PKG_CONFIG}'
rust = ['rustc', '--target', '${RUST_TARGET}' ,'--sysroot', '${XBPS_CROS
S_BASE}/usr']
g-ir-scanner = '${XBPS_CROSS_BASE}/usr/bin/g-ir-scanner'
- g-ir-compiler = '${XBPS_CROSS_BASE}/usr/bin/g-ir-compiler'
- g-ir-generate = '${XBPS_CROSS_BASE}/usr/bin/g-ir-generate'
+ g-ir-compiler = '${XBPS_CROSS_BASE}/usr/bin/gi-compile-repository'
+ g-ir-generate = '${XBPS_CROSS_BASE}/usr/bin/gi-decompile-typelib'
llvm-config = '/usr/bin/llvm-config'
cups-config = '${XBPS_CROSS_BASE}/usr/bin/cups-config'
```
It seems to work, although looking through it, there are some things that can potentially be improved.
Currently we use a fork of prelink-cross to get prelink-rtld to get the recursive dependencies from DT_NEEDED in an lld-like output. I'm not sure this is needed and it can probably be simplified by just using elfutils (which is already a dependency of glib) like what Debian does: https://salsa.debian.org/gnome-team/gobject-introspection/-/blob/debian/latest/debian/elf-get-needed.c (That needs testing though)
That method was also brought up upstream by the Debian maintainer: https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/482
Another thing I noticed is that Debian wraps all of the `g-ir-*`/`gi-*` tools with qemu:
https://salsa.debian.org/gnome-team/glib/-/blob/debian/latest/debian/rules?ref_type=heads#L72-91
Not sure how necessary that is, but in meson we pass the raw unwrapped `g-ir-generate` (equivalent of `gi-decompile-typelib` in glib):
https://github.com/void-linux/void-packages/blob/master/common/build-helper/meson.sh#L71
I don't think that works unless `build_helper=qemu` is specified, although there probably isn't much using it.
I'll worry about this more later.
next prev parent reply other threads:[~2024-03-22 8:03 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 20:10 [PR PATCH] " oreo639
2024-03-21 20:22 ` [PR PATCH] [Updated] [WIP] " oreo639
2024-03-21 20:23 ` oreo639
2024-03-21 20:50 ` oreo639
2024-03-21 21:04 ` oreo639
2024-03-21 21:08 ` chrysos349
2024-03-21 21:16 ` oreo639
2024-03-21 21:18 ` oreo639
2024-03-21 21:24 ` [PR PATCH] [Updated] " oreo639
2024-03-21 21:31 ` oreo639
2024-03-22 0:15 ` oreo639
2024-03-22 0:48 ` oreo639
2024-03-22 7:29 ` oreo639
2024-03-22 7:58 ` oreo639
2024-03-22 7:58 ` oreo639
2024-03-22 8:00 ` oreo639
2024-03-22 8:03 ` oreo639 [this message]
2024-03-22 8:19 ` oreo639
2024-03-22 8:20 ` oreo639
2024-03-22 8:20 ` oreo639
2024-03-22 8:20 ` oreo639
2024-03-22 8:22 ` oreo639
2024-03-22 23:13 ` [PR PATCH] [Updated] " oreo639
2024-03-23 0:09 ` oreo639
2024-03-23 0:12 ` [PR PATCH] [Updated] " oreo639
2024-03-23 0:14 ` oreo639
2024-03-24 9:14 ` oreo639
2024-04-14 8:38 ` [PR PATCH] [Updated] " oreo639
2024-04-14 21:44 ` oreo639
2024-04-17 2:23 ` oreo639
2024-04-17 2:32 ` oreo639
2024-04-17 2:37 ` oreo639
2024-04-17 2:40 ` [PR PATCH] [Updated] " oreo639
2024-04-17 2:44 ` oreo639
2024-04-17 2:46 ` oreo639
2024-04-17 2:53 ` [PR PATCH] [Updated] " oreo639
2024-04-17 2:53 ` oreo639
2024-04-17 3:21 ` oreo639
2024-04-17 3:36 ` oreo639
2024-04-17 3:47 ` [PR PATCH] [Updated] " oreo639
2024-04-17 3:49 ` oreo639
2024-04-17 23:36 ` oreo639
2024-04-18 0:28 ` oreo639
2024-04-18 3:02 ` oreo639
2024-04-18 3:25 ` [PR PATCH] [Merged]: " oreo639
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240322080335.0A75C22105@inbox.vuxu.org \
--to=oreo639@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).