How to exclude host versions of Qt libraries from Yocto SDK / toolchain

petero3

How practical / desirable is it to exclude the host versions of the Qt libraries from our Yocto SDK / toolchain?

e.g. for comparison Boot2Qt for Raspberry Pi includes not just the target/armv8 versions of all the Qt6 libraries, but also all the host/x86 versions.

Even though the host versions are available via Qt / Qt 6.8.3 / Desktop anyway.

/data/Qt$ find . -name libQt6QuickEffects.so
./6.8.3/gcc_64/lib/libQt6QuickEffects.so
./6.8.3/Boot2Qt/raspberrypi-armv8/toolchain/sysroots/cortexa53-poky-linux/usr/lib/libQt6QuickEffects.so
./6.8.3/Boot2Qt/raspberrypi-armv8/toolchain/sysroots/x86_64-pokysdk-linux/usr/lib/libQt6QuickEffects.so

In our own Yocto (for NXP i.MX 8X) we also have host versions of all the Qt6 libraries.
But without Virtual Keyboard.
And we need to install Qt for Desktop anyway.
Therefore the host versions in the SDK seem redundant and consume extra build time and space in the SDK.

Obviously certain tools for host, like moc, are needed to cross-compile for target.
Why are all the graphical/multimedia etc libraries included for host too though?
Is there a standard way to only build/package the bare minimum of Qt for host for cross-compiling?

Docs link for reference:
https://doc.qt.io/Boot2Qt/b2qt-meta-qt6.html