5e3a61b40b
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>
Poky
Poky is an integration of various components to form a complete prepackaged build system and development environment. It features support for building customised embedded device style images. There are reference demo images featuring a X11/Matchbox/GTK themed UI called Sato. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK with IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of layers which extend the systems capabilities in a modular way.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation and various sources of information e.g. for the hardware support. Poky is in turn a component of the Yocto Project.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at: http://yoctoproject.org/documentation
OpenEmbedded-Core is a layer containing the core metadata for current versions of OpenEmbedded. It is distro-less (can build a functional image with DISTRO = "") and contains only emulated machine support.
For information about OpenEmbedded, see the OpenEmbedded website: http://www.openembedded.org/