sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

documentation: poky-ref-manual - Updates to faq entry 

Ensure that this section correctly and accurately describes how Poky and
OE relate to eachother currently.  The faq entry changed is
"How does Poky differ from OpenEmbedded?"

(From yocto-docs rev: ecc88ef12ec2faa48d05824e8b781a7d43e86127)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Paul Eggleton 2012-10-02 09:24:47 -07:00 committed by Richard Purdie
parent 5a18ea1b00
commit 7067717113
1 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
documentation/poky-ref-manual/faq.xml
View File

@ -13,14 +13,16 @@
</question>
<answer>
<para>
The term "Poky" is sometimes used to refer to the build system that the
Yocto Project uses.
The build system used in the Yocto project is referred to as the
OpenEmbedded build system because "Poky" was derived from <ulink
url='&OE_HOME_URL;'>OpenEmbedded</ulink>.
Poky is a stable, smaller subset focused on the mobile environment.
Development in the Yocto Project using Poky is closely tied to OpenEmbedded with
features being merged regularly between the two for mutual benefit.
The term "Poky" refers to the specific reference build system that
the Yocto Project provides.
Poky is based on <ulink url='&YOCTO_DOCS_DEV_URL;#oe-core'>OE-Core</ulink>
and BitBake.
Thus, the generic term used here for the build system is
the "OpenEmbedded build system."
Development in the Yocto Project using Poky is closely tied to OpenEmbedded, with
changes always being merged to OE-Core or BitBake first before being pulled back
into Poky.
This practice benefits both projects immediately.
For a fuller description of the term "Poky", see the
<ulink url='&YOCTO_DOCS_DEV_URL;#poky'>poky</ulink> term in the Yocto Project
Development Manual.