From: Gyorgy Sarvari <skandigraun@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-oe][PATCH] nodejs: ignore QEMU_OPTIONS for native signature generation
Date: Sat, 21 Jun 2025 21:41:14 +0200 [thread overview]
Message-ID: <aa7dd813-5bfc-4ed5-9d02-11c62577bb26@gmail.com> (raw)
In-Reply-To: <184B26232F1A96E9.12316@lists.openembedded.org>
This is of course an RFC too, just very small.
I noticed that every time I switch target machine, nodejs-native is
being rebuilt (starting with Scarthgap), which sometimes means
recompiling it 4 times, on all Yocto versions.
Looking at the recipe I believe that qemu is really only used when the
target and build CPU has different bitness, but I'm not that familiar
with the internals of nodejs build process - if someone more familiar
with it could share their opinion on this proposal, that would be helpful.
next parent reply other threads:[~2025-06-21 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <184B26232F1A96E9.12316@lists.openembedded.org>
2025-06-21 19:41 ` Gyorgy Sarvari [this message]
2025-06-22 16:35 ` [oe] [meta-oe][PATCH] nodejs: ignore QEMU_OPTIONS for native signature generation Gyorgy Sarvari
2025-06-21 19:40 Gyorgy Sarvari
2025-06-23 5:35 ` [oe] " Alexander Kanavin
2025-06-23 5:57 ` Gyorgy Sarvari
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=aa7dd813-5bfc-4ed5-9d02-11c62577bb26@gmail.com \
--to=skandigraun@gmail.com \
--cc=openembedded-devel@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.