6714a6c59a
Following fixes:
dev-manual - Discovered a <ulink> tag that was not a single
line. These types of links need to not have hard
returns. If they do, mega-manual.sed will not
process the link. Changed the reference to a
single line.
kernel-dev - Discovered that I had the old poky.ent variable
(i.e. YOCTO_DOCS_KERNEL_URL) as part of the link
in the opening note on the title page. I changed
it to the proper variable, which is
YOCTO_DOCS_KERNEL_DEV_URL. The old link was not
being processed by mega-manual.sed.
profile-manual - First problem was the wrong manual title in
a <ulink> tag, which caused the mega-manual.sed
file to skip processing the link into a non-link.
Second problem was on the title page. Incredulously,
I had the title of the manual reversed for Chapter
1. Fixed it.
(From yocto-docs rev: 71dedd610dce9fdc6472a5cf2b18ec8729d77e55)
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 = "") 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.