dfd6c546c4
Adds a SPLASH_IMAGES variable which you can set to include one or more images (listed in URI form as they would appear in SRC_URI), and an executable will be built for each one, with each executable packaged separately and managed at runtime using the alternatives system. An optional "outsuffix" parameter can be used to specify the suffix for the executable/package name. The images themselves can either be pre-processed image header files (produced using the make-image-header.sh script that comes with psplash), or alternatively you can provide a .png and it will be converted using the aforementioned script on the fly (at the expense of requiring gdk-pixbuf-native at build time). This has been implemented in such a way that you can still just provide your own psplash-poky-img.h in a bbappend and it will work as it did before; the only change being that the psplash executable is provided in a "psplash-default" package rather than in the main psplash package, and an RRECOMMENDS is set up to ensure psplash-default gets pulled in (if you specify your own file or change the outsuffix you will need to either install it separately yourself or add your own RRECOMMENDS relationship.) Implements [YOCTO #1947] (From OE-Core rev: d3de5f7308b4a42b809884119a670af5bedde38f) Signed-off-by: Paul Eggleton <paul.eggleton@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/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/