[UX][Bug docs: Warning occurs after building zephyr for Transparent Gateway & Doorlock BP
The module affected
https://docs.oniroproject.org/projects/blueprints/doorlock.html#build-the-software
What is the action to reproduce the bug? (Steps to reproduce)
Build Transparent Gateway
build-oniro-mesh-node DISTRO=oniro-zephyr-blueprint-gateway MACHINE=arduino-nano-33-ble bitbake zephyr-blueprint-gateway-node
Build Doorlock
build-oniro-mesh-node DISTRO=oniro-zephyr-blueprint-gateway MACHINE=arduino-nano-33-ble bitbake zephyr-blueprint-gateway-node
What is the result you see? (Actual result)
WARNINGS:
➜ build-oniro-mesh-node DISTRO=oniro-zephyr-blueprint-gateway MACHINE=arduino-nano-33-ble bitbake zephyr-blueprint-gateway-node
WARNING: You have included the meta-tpm layer, but 'tpm or tpm2' has not been enabled in your DISTRO_FEATURES. Some bbappend files and preferred version setting may not take effect. See the meta-tpm README for details on enabling tpm support.
WARNING: You have included the meta-virtualization layer, but 'virtualization' has not been enabled in your DISTRO_FEATURES. Some bbappend files may not take effect. See the meta-virtualization README for details on enabling virtualization support.
➜ build-oniro-mesh-node DISTRO=oniro-zephyr-blueprint-gateway MACHINE=arduino-nano-33-ble bitbake zephyr-blueprint-gateway-node
WARNING: You have included the meta-tpm layer, but 'tpm or tpm2' has not been enabled in your DISTRO_FEATURES. Some bbappend files and preferred version setting may not take effect. See the meta-tpm README for details on enabling tpm support.
WARNING: You have included the meta-virtualization layer, but 'virtualization' has not been enabled in your DISTRO_FEATURES. Some bbappend files may not take effect. See the meta-virtualization README for details on enabling virtualization support.
What is the result you expect? (Expected behaviour)
no Warnings
Frequency? (always, sometimes, one-time issue)
Always
Tested version (image name and version, platform)
Kirkstone
Do you know any workaround of this issue? (link to workaround/mitigation steps etc)
n/a
Do you have a fix for this issue?
n/a