cf60f95d9f
This fixes the hang issue encountered with parse errors. The underlying issue seems to have been the pool.terminate(). This sends SIGTERM to each of the multiprocessing pool's processes, however, a python process terminating in this fashion can corrupt any queues it's interacting with, causing a number of problems for us (e.g. the queue that sends events to the UI). So instead of using multiprocessing's pool, we roll our own, with the ability to cancel the work. In the very long term, the python concurrent.futures module introduced in python 3.2 could be used to resolve this as well. (Bitbake rev: 7c39cfd8e060cca8753ac4114775447b18e13067) Signed-off-by: Christopher Larson <chris_larson@mentor.com> 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/community/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/