Now we have settled on best practises and compliance criteria, bring meta-yocto
into compliance by separating out the hardware support components into
meta-yocto-bsp leaving policy configuration in meta-yocto.
Also rename the meta-yocto scripts directory to OE-Core can be a clearly
isolated component in poky.
(From meta-yocto rev: eac90e27a032ea23d9a4f35c7eef8b1940c80e22)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Many people are seeing issues from the empty path warnings from BBPATH.
The empty path entry corresponding to the current working directory is a
problem since if cwd changes, so does BBPATH and build reproducibility.
Simply removing the empty element causes problems since the build
directory then isn't listed in BBPATH which means local.conf isn't found
and this gives an extremely confusing error message about bbappends
being unsatisfied.
The build directory in bitbake terms is TOPDIR. The correct way to fix
things is to add in TOPDIR into bblayers.conf itself. This means the
layers can happily append/prepend to BBPATH at will as its no longer
empty hence neatly solving all the various problems. Since the file has
changed, the version is also changed.
(From meta-yocto rev: 7bbbedf64b0820cacffe723789486d3081894827)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Hob may dynamically sets BBLAYERS to bitbake server, thus we need a
flexible way to load BBLAYERS value.
(From OE-Core rev: 458d0f8b39e7d9dce544f53c65e2a6ffae21ad24)
Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie
Dongxiao Xu
Joshua Lock