diff options
author | Gyorgy Sarvari <skandigraun@gmail.com> | 2025-06-27 16:13:06 +0200 |
---|---|---|
committer | Khem Raj <raj.khem@gmail.com> | 2025-06-28 11:04:24 -0700 |
commit | b2a950a75b15c93f625bfe6514bc248c9310813f (patch) | |
tree | dec576c30b7480cc89c31cefc0da2c14ec6ecf42 /meta-python/recipes-devtools/python/python3-lazy-object-proxy_1.11.0.bb | |
parent | 87d1e803f5a3e5998714260ef7fcec2848059d1c (diff) | |
download | meta-openembedded-b2a950a75b15c93f625bfe6514bc248c9310813f.tar.gz |
nodejs: inherit qemu class conditionally
The recipe unconditionally inherits the qemu class, because it executes
some target binaries when it is cross-compiled and the bit-width of the
build host and the target host are different.
Since it is unconditional, it also means that it is inherited for native
and nativesdk builds also. The qemu class uses some qemu options that are
always derived from the target machine's configuration, even when the
recipe is built for class-native. This means that some of the variables
used by the recipe changes (e.g. QEMU_OPTIONS), and the shared state cache
is invalidated when the target machine changes, even when nodejs-native is
being built - and it triggers a full rebuild of nodejs-native unnecessarily.
To avoid this, inherit the qemu class conditionally, only in case it is
used (when the target and build arch's bit-widths are different).
Also, inherit qemu-native based on the same condition, and move around the
qemu-dependent code a bit, so it will be only executed when the qemu class
is inherited.
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python3-lazy-object-proxy_1.11.0.bb')
0 files changed, 0 insertions, 0 deletions