b030c4b498
When using conditional override syntax, this should only be combined with the append/prepend/remove operators. This commit rewrites the claas-native and class-target overrides such that it does not replace any recipe set values of EXTRA_OECMAKE (reading the removed syntax it is very counter-intuitive, but sadly really happens). The problem was: EXTRA_OECMAKE:class-target += " foo" # from class EXTRA_OECMAKE += " baa" # from recipe to be evaluated to EXTRA_OECMAKE = " foo". By this change, the values are appended as expected, even if the recipe is not using conditional overrides for the value assignment.
Dependencies
This layer depends on:
URI: git://github.com/meta-qt5/meta-qt5 branch: master
URI: git://git.openembedded.org/bitbake branch: master
URI: git://git.openembedded.org/openembedded-core layers: meta branch: master
Patches
Please submit any patches against the kf5 layer on KDE GitLab project. Project available on https://invent.kde.org/packaging/yocto-meta-kf5 GitLab guide on https://community.kde.org/Infrastructure/GitLab
Table of Contents
I. Adding the kf5 layer to your build II. KF5
I. Adding the kf5 layer to your build
In order to use this layer, you need to make the build system aware of it.
Assuming the kf5 layer exists at the top-level of your yocto build tree, you can add it to the build system by adding the location of the kf5 layer to bblayers.conf, along with any other layers needed. e.g.:
BBLAYERS ?= "
/path/to/poky/meta
/path/to/poky/meta-yocto
/path/to/poky/meta-yocto-bsp
/path/to/meta-openembedded/meta-networking
/path/to/meta-openembedded/meta-python
/path/to/meta-openembedded/meta-oe
/path/to/yocto/meta-kf5
/path/to/yocto/meta-qt5
"
II. KF5
KF5, or KDE Frameworks 5, are a set of Qt add-on modules developed by the KDE project. They extend and improve on Qt. User documentation can be found here:
http://api.kde.org/frameworks-api/frameworks5-apidocs/
Information regarding the development of KF5 can be found here: