follow Richard's approach, modify bzip2-native recipe to install bzip2 package binaries to STAGING_BINDIR_NATIVE/bzip2-native to avoid problems when other package is doing upack to reference bzip2. libbz2.so* still installs to STAGING_LIBDIR_NATIVE. change python-native to depends on bzip2-replacement-native instead of bzip2-full-native and add EXTRANATIVEPATH for bzip2-native. Didn't add bzip2native.bbclass as python-native is the only user so far. (From OE-Core rev: 5bf3541836457465aa76577bfb41cdf6316213c9) Signed-off-by: Yao Zhao <yao.zhao@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.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/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/