mirror of
https://git.yoctoproject.org/poky
synced 2026-05-08 05:09:24 +00:00
481c1788bcf4a37a7eb9a6ce4d0fe00d6df29827
The way the mega-manual used 'xinclude' to suck in the other YP manuals was to suck in the root XML file. The problem with this was that the root XML file for each subsequent book would include front-matter information. The front-matter information included an .authorgroup style, which caused the new mega-manual title displayed at the very top to be also re-displayed with a subsequent manual's title. These changes altered the strategy for using 'xinclude' to pull in the various YP manuals. Rather than pull in the root XML file for a given manual, individual chapters are pulled in that comprise a given manual. A slight side-effect is that chapter numbering is sequential from top to bottom in the mega-manual, which I suppose is better as it is being presented as an entire manual anyway. (From yocto-docs rev: 61cc9f2f92900894ef09ff13e1e92ebe30a17be3) 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/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 = "nodistro") and contains only emulated machine support.
For information about OpenEmbedded, see the OpenEmbedded website:
http://www.openembedded.org/
Where to Send Patches
=====================
As Poky is an integration repository, patches against the various components
should be sent to their respective upstreams.
bitbake:
bitbake-devel@lists.openembedded.org
meta-yocto:
poky@yoctoproject.org
Most everything else should be sent to the OpenEmbedded Core mailing list. If
in doubt, check the oe-core git repository for the content you intend to modify.
Before sending, be sure the patches apply cleanly to the current oe-core git
repository.
openembedded-core@lists.openembedded.org
Note: The scripts directory should be treated with extra care as it is a mix
of oe-core and poky-specific files.
Description