Skip to content
Snippets Groups Projects
Commit 4d96d82f authored by Stefan Schmidt's avatar Stefan Schmidt
Browse files

flavours: unify and symlink bblayers between different flavours


Our bblayers file diverged between the different flavours and e.g. the
meta-ohos-foundation was still present for zephyr and freertos.

We enable all layers on all flavours. The only overhead should be in
parsing the recipes. If something else breaks we consider this a bug
worth fixing.

The usage of symlinks should be safe here. Yocto buildhost will almost
always be Linux based, but it this should even work on Windows by now.
If we run into trouble with this we can always got back to three files.

Signed-off-by: default avatarStefan Schmidt <stefan.schmidt@huawei.com>
parent 9f4e514e
No related branches found
No related tags found
No related merge requests found
# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
POKY_BBLAYERS_CONF_VERSION = "2"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
##OEROOT##/meta \
##OEROOT##/meta-poky \
##OEROOT##/meta-yocto-bsp \
##OEROOT##/../meta-freertos \
##OEROOT##/../meta-ohos/meta-ohos-foundation \
"
../linux/bblayers.conf.sample
\ No newline at end of file
......@@ -9,6 +9,8 @@ BBLAYERS ?= " \
##OEROOT##/meta \
##OEROOT##/meta-poky \
##OEROOT##/meta-yocto-bsp \
##OEROOT##/../meta-freertos \
##OEROOT##/../meta-zephyr \
##OEROOT##/../meta-ohos/meta-ohos-core \
##OEROOT##/../meta-ohos/meta-ohos-acts \
##OEROOT##/../meta-intel \
......
# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
POKY_BBLAYERS_CONF_VERSION = "2"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
##OEROOT##/meta \
##OEROOT##/../meta-openembedded/meta-oe \
##OEROOT##/../meta-openembedded/meta-python \
##OEROOT##/../meta-zephyr \
##OEROOT##/../meta-ohos/meta-ohos-core \
##OEROOT##/../meta-ohos/meta-ohos-foundation \
"
../linux/bblayers.conf.sample
\ No newline at end of file
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment