Integrate meta-seco-edgehog-embedded/qt6_integration
[PACKAGEGROUP][QT6] Remove statement duplicated by mistake
[IMAGE][EDGEHOG-FULL][QT] Dynamic inclusion of Qt5 or Qt6
The image inherits the right class and uses the desidered packagegroup (regarding Qt) depending to the vaule of the global variable
EDGEHOG_QT_VERSION (["5.x" | "6.x"])
--
[DISTO][QT VERSION] Qt version selection via global variable
The variable EDGEHOG_QT_VERSION have to be set for the selection of the desidered version. Possible values:
"5.x" -> select the layer Qt5 "6.x" -> select the layer Qt6
Default value: "5.x"
Note: The setting of it should be done at project level, placing the assignment instruction inside of local.conf file (e.g. EDGEHOG_QT_VERSION = "6.x" ) The selection of the desidered version is not included into configuration tool (not yet).
Note: Also the configuration of bblayer file inside the project required a manual editing: replace
${BSPDIR}/layers/meta-qt5 \
with
${BSPDIR}/layers/meta-qt6 \
(for custom project where Qt6 is a must, the following lines are added into custom bblayer file:
BBLAYERS:remove = " ${BSPDIR}/layers/meta-qt5 "
BBLAYERS += "
${BSPDIR}/layers/meta-qt6
"
)
--
[QT6][PACKAGEGROUP] Add Qt6 packagegroup with common packages inside
Included packages:
- Font
- QtQuick3D
- base
- tools
- traslations
(Actually, examples group missing)
--
[QT BASE] Bring qt5 recipes into dynamic layer
This is the fist step for the introduction of the Qt6. The two versions (5.x and 6.x) have to coexist and the selection of one of them will be dynamic. Placing all the recipes regarding qt5 (and in the next time qt6 also) in a dynamic layer we are able to avoid them without error at compile time if qt5 is not a selected feature.