From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: "Böszörményi Zoltán" <zboszor@gmail.com>,
openembedded-core <openembedded-core@lists.openembedded.org>,
"Alexander Kanavin" <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH v2] glib/gobject-introspection: update 2.78.4 -> 2.80.0, 1.78.1 -> 1.80.0
Date: Mon, 13 May 2024 18:00:56 +0200 [thread overview]
Message-ID: <CANNYZj85avnQgr=i_mp551nLuv8oVPLS2urN8nm2nxBo2sww5w@mail.gmail.com> (raw)
In-Reply-To: <AD01E4CD-6C57-4D17-8C7B-E4AFB0C01C12@arm.com>
On Mon, 13 May 2024 at 17:53, Ross Burton <Ross.Burton@arm.com> wrote:
> > That chain happens only when gobject-introspection-data is in distro
> > features, and that is only present for target builds, not native or
> > nativesdk.
>
> There is a long-standing goal for G-I to work in both native and nativesdk, so I’m curious if this is the sole blocker for nativesdk to work.
I don't know. You first need to specifically add
gobject-introspection-data to nativesdk distro features, and then all
kinds of things are likely going to break, even if BBCLASSEXTEND is
set correctly everywhere. This is very much out of scope for this
version update.
Alex
prev parent reply other threads:[~2024-05-13 16:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 10:32 [PATCH v2] glib/gobject-introspection: update 2.78.4 -> 2.80.0, 1.78.1 -> 1.80.0 Alexander Kanavin
2024-05-07 4:38 ` [OE-core] " Mittal, Anuj
2024-05-07 15:46 ` Ross Burton
2024-05-10 9:52 ` Alexander Kanavin
2024-05-10 10:01 ` Ross Burton
2024-05-07 15:52 ` Ross Burton
2024-05-07 20:25 ` Alexander Kanavin
[not found] ` <17CD4EAB9E2E17EE.17376@lists.openembedded.org>
2024-05-10 9:48 ` Alexander Kanavin
2024-05-07 16:02 ` Ross Burton
2024-05-13 14:27 ` Böszörményi Zoltán
2024-05-13 14:42 ` Alexander Kanavin
2024-05-13 15:53 ` Ross Burton
2024-05-13 16:00 ` Alexander Kanavin [this message]
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='CANNYZj85avnQgr=i_mp551nLuv8oVPLS2urN8nm2nxBo2sww5w@mail.gmail.com' \
--to=alex.kanavin@gmail.com \
--cc=Ross.Burton@arm.com \
--cc=alex@linutronix.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=zboszor@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).