From: "Jörg Sommer" <joerg.sommer@navimatix.de>
To: Qi.Chen@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] runqemu: restore support to run without bitbake
Date: Thu, 29 Jan 2026 16:48:22 +0100 [thread overview]
Message-ID: <aXuAZarEFLu0TITT@navimatix.de> (raw)
In-Reply-To: <20260129030811.104017-1-Qi.Chen@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]
Chen Qi via lists.openembedded.org schrieb am Do 29. Jan, 11:08 (+0800):
> From: Chen Qi <Qi.Chen@windriver.com>
>
> This patch is basically a revert of the following three patches:
> - 0c10a78796 scripts/runqemu: raise an error when bitbake was not found
> - b931f74442 scripts/runqemu: remove the code block that works around the missing bitbake environment
> - 8197be4dd3 runqemu: ensure that bitbake environment is either returned, or an exception is raised
>
> The comment is also changed to reflect the current usage:
> "invoked from a running bitbake instance" ->
> "invoked from environment with no bitbake (e.g., SDK)"
>
> This code path was deleted by accident based on the reason that nobody
> is using it. But in fact, running runqemu from SDK needs this code path.
> Such case has been supported for years.
By the way: I use runqemu (version from kirkstone) without bitbake, because
bitbake is in a docker container (kas-container):
OECORE_NATIVE_SYSROOT=/ runqemu ....qemuboot.conf
Regards Jörg
--
Navimatix GmbH T: 03641 - 327 99 0
Tatzendpromenade 2 F: 03641 - 526 306
07745 Jena www.navimatix.de
Geschäftsführer: Steffen Späthe, Jan Rommeley
Registergericht: Amtsgericht Jena, HRB 501480
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5000 bytes --]
prev parent reply other threads:[~2026-01-29 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 3:08 [OE-core][PATCH] runqemu: restore support to run without bitbake Qi.Chen
2026-01-29 9:57 ` Alexander Kanavin
2026-01-30 2:58 ` ChenQi
2026-01-29 15:48 ` Jörg Sommer [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=aXuAZarEFLu0TITT@navimatix.de \
--to=joerg.sommer@navimatix.de \
--cc=Qi.Chen@windriver.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox