baf536c62c
I made several changes based on feedback from Jessica Zhang. 1. Removed "SDKVERSION" as a way of identifying the directory in which a toolchain tarball is installed. I replaced with "1.1" 2. Cleaned up the bitbake command verbage to consistently use 'bitbake' command. 3. Cleaned up an erroneous reference to the toolchain environment setup scripts. I was referring the user to the oe-init-build-env area. 4. Changed wording to indicate that the toolchain tarball is generated after running bitbake rather than installing the toolchain. 5. Replaced the gmae tarball file used in an example to be the regular taball. (From yocto-docs rev: f7c3e4f4a666121a29825099d451eab1accb0616) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@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
For information about OpenEmbedded see their website: http://www.openembedded.org/