What are you trying to accomplish, why are you trying to get rid of qemu and
which version of the Yocto Project are you using?
You need some qemu support for parts of the system to function properly. They
expect on arm/aarch64 hardware to be able to run test scripts and/or
post-install scripts as the target architecture during the root filesystem
generation.
The dependencies for qemu based items are ingrained into the base system
configuration.
For instance, if the filesystem type of 'qemu-sd' is enabled (and it is in most
configurations), then a dependency on qemu-xilinx-system-native will be introduced.
On 1/19/23 2:56 PM, David Babich wrote:
I've been trying in vain to remove all qemu support from my custom build. I've
add the following to my distro.conf file:
PNBLACKLIST[qemu]="blacklist"
PNBLACKLIST[qemu-native]="blacklist"
PNBLACKLIST[qemu-helper-native]="blacklist"
PNBLACKLIST[qemu-helper-native-dev]="blacklist"
PNBLACKLIST[qemu-system-native]="blacklist"
#PNBLACKLIST[qemu-xilinx]="blacklist"
#PNBLACKLIST[qemu-xilinx-native]="blacklist"
#PNBLACKLIST[qemu-xilinx-system-native]="blacklist"
PNBLACKLIST[nativesdk-qemu]="blacklist"
PNBLACKLIST[nativesdk-qemu-helper]="blacklist"
PNBLACKLIST[nativesdk-packagegroup-sdk-host]="blacklist"
MACHINE_FEATURES_BACKFILL_CONSIDERED = " \
qemu-usermode \
"
However when I uncomment the qemu-xilinx, qemu-xilinx-native and
qemu-xilinx-system-native I get errors indicating unbuildable dependencies for
those missing packages. I've also tried adding them to PACKAGE_EXCLUDE,
IMAGE_FEATURES:remove, DISTRO_FEATURES:remove, and IMAGE_INSTALL:remove with no
luck. There must be some way to completely disable this without forking the
meta-xilinx layers and manually removing them.
If I could understand your use-case and reason to disable them, I might be able
to suggest something. But generally, no you can't just completely disable qemu
without significantly changing aspects of the system as a whole.
At a minimum you will want to remove (and resolve dangling references to):
meta-xilinx-core/conf/machine/include/machine-xilinx-qemu.inc
meta-xilinx-core/classes/image-types-xilinx-qemu.bbclass
PNBLACKLIST or SKIP_RECIPE
If you are simply trying to ensure that qemu never goes to the target image,
then you only need to skip qemu/qemu-xilinx.
The qemu-*native and nativesdk-qemu* packages are helpers during compilation
time and do not get deployed into the target image.
--Mark
Thanks in advance for any help.
-David
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5129):
https://lists.yoctoproject.org/g/meta-xilinx/message/5129
Mute This Topic: https://lists.yoctoproject.org/mt/96386630/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
