c7e4a6ae2c
I discovered a bug when publishing documents. There are two scp commands that copy a document's files and figures to the appropriate directory in the srifenbark@yocto-www:~/www.yoctoproject.or-docs server where the manuals are published. The second scp command had a "/figures" at the end. This was causing a new "figures" directory to be created within the "figures" directory. This redundancy shows up as missing figures in the manuals if a new figure or changed figure is ever added to the book after initial publishing. I removed the extra "/figures" at the end of the scp command. (From yocto-docs rev: 5ab530f998427405a0486b94ca76cff58a4cf463) 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
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/