Building meta-virtualization layer in yocto


Keywords:linux 


Question: 

I am trying to add the meta-virtualization layer in my yocto project. The layer depends on openembedded-core and multiple layers provided by meta-openembedded. Following is the structure of my bblayers.conf file after adding the meta-virtualization layer and it's dependencies.

BBLAYERS ?= " \
/home/mshehery/Downloads/git/Yocto/poky/meta \
/home/mshehery/Downloads/git/Yocto/poky/meta-yocto \
/home/mshehery/Downloads/git/Yocto/poky/meta-yocto-bsp \
/home/mshehery/Downloads/git/Yocto/poky/meta-oe \
/home/mshehery/Downloads/git/Yocto/poky/meta-virtualization \
/home/mshehery/Downloads/git/Yocto/poky/meta-networking \
/home/mshehery/Downloads/git/Yocto/poky/meta-filesystems \
/home/mshehery/Downloads/git/Yocto/poky/meta-python \
"

However, when I try to build docker present in the meta-virtualization layer, I encounter the following error

WARNING: Host distribution "Ubuntu-16.04" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
Loading cache: 100% |####################################################################################################################################################| ETA:  00:00:00
Loaded 1078 entries from dependency cache.
NOTE: Error during finalise of /home/mshehery/Downloads/git/Yocto/poky/meta-oe/recipes-devtools/tcltk/tk_8.6.6.bb                                                        | ETA:  --:--:--
ERROR: ParseError at /home/mshehery/Downloads/git/Yocto/poky/meta-oe/recipes-connectivity/libqmi/libqmi_1.16.0.bb:12: Could not inherit file classes/bash-completion.bbclass

If I am not wrong, the current versions of the yocto project use openembedded as their build system. So, is there any need to integrate the openembedded-core into my yocto project to add the meta-virtualization layer, or is it already present in the yocto project by default?


1 Answer: 

Short summary of the discussion:

  • Use the same release branch for all your layers (unless you really know what you do.

  • Check that all your layers are activated in bblayers.conf.