From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andrej Valek <andrej.v@skyrain.eu>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] perf: nativesdk
Date: Thu, 19 Jun 2025 13:45:48 +0100 [thread overview]
Message-ID: <97a02d26042945f79cdc8a4a7099afbf93079d6b.camel@linuxfoundation.org> (raw)
In-Reply-To: <3647d65b-e79b-46e4-83e9-46b17762934b@skyrain.eu>
On Thu, 2025-06-19 at 13:44 +0200, Andrej Valek wrote:
> Yes I know, that is bad, but I solved it already with other way.
>
> On the other hand, maybe the lines in kernel-yocto.bbclass should be
> target specific.
>
> do_kernel_configme[depends] +=
> "virtual/${TARGET_PREFIX}binutils:do_populate_sysroot"
> do_kernel_configme[depends] +=
> "virtual/${TARGET_PREFIX}gcc:do_populate_sysroot"
>
> I think, that dependency to gcc-cross was done like:
>
> linux[do_kernel_configme] -> gcc-cross-aarch64 -> linux-libc-headers.
It won't be those. kernel.bbclass does:
DEPENDS += "virtual/cross-binutils virtual/cross-cc kmod-native bc-native bison-native"
[...]
# we include gcc above, we dont need virtual/libc
INHIBIT_DEFAULT_DEPS = "1"
and virtual/cross-cc will expand to gcc-cross-aarch64.
There is an assumption that nobody uses nativesdk with kernel.bbclass
in multiple places.
Cheers,
Richard
next prev parent reply other threads:[~2025-06-19 12:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 7:53 perf: nativesdk Andrej Valek
2025-06-19 7:56 ` [OE-core] " Alexander Kanavin
2025-06-19 8:07 ` Andrej Valek
2025-06-19 8:13 ` Alexander Kanavin
2025-06-19 8:59 ` Marko, Peter
2025-06-19 10:57 ` Andrej Valek
2025-06-19 11:21 ` Richard Purdie
2025-06-19 11:44 ` Andrej Valek
2025-06-19 12:45 ` Richard Purdie [this message]
2025-06-19 12:55 ` Andrej Valek
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=97a02d26042945f79cdc8a4a7099afbf93079d6b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=andrej.v@skyrain.eu \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.