diff options
| -rw-r--r-- | documentation/poky-ref-manual/faq.xml | 18 |
1 files changed, 10 insertions, 8 deletions
diff --git a/documentation/poky-ref-manual/faq.xml b/documentation/poky-ref-manual/faq.xml index c1a1390b36..943d22a7d8 100644 --- a/documentation/poky-ref-manual/faq.xml +++ b/documentation/poky-ref-manual/faq.xml | |||
| @@ -13,14 +13,16 @@ | |||
| 13 | </question> | 13 | </question> |
| 14 | <answer> | 14 | <answer> |
| 15 | <para> | 15 | <para> |
| 16 | The term "Poky" is sometimes used to refer to the build system that the | 16 | The term "Poky" refers to the specific reference build system that |
| 17 | Yocto Project uses. | 17 | the Yocto Project provides. |
| 18 | The build system used in the Yocto project is referred to as the | 18 | Poky is based on <ulink url='&YOCTO_DOCS_DEV_URL;#oe-core'>OE-Core</ulink> |
| 19 | OpenEmbedded build system because "Poky" was derived from <ulink | 19 | and BitBake. |
| 20 | url='&OE_HOME_URL;'>OpenEmbedded</ulink>. | 20 | Thus, the generic term used here for the build system is |
| 21 | Poky is a stable, smaller subset focused on the mobile environment. | 21 | the "OpenEmbedded build system." |
| 22 | Development in the Yocto Project using Poky is closely tied to OpenEmbedded with | 22 | Development in the Yocto Project using Poky is closely tied to OpenEmbedded, with |
| 23 | features being merged regularly between the two for mutual benefit. | 23 | changes always being merged to OE-Core or BitBake first before being pulled back |
| 24 | into Poky. | ||
| 25 | This practice benefits both projects immediately. | ||
| 24 | For a fuller description of the term "Poky", see the | 26 | For a fuller description of the term "Poky", see the |
| 25 | <ulink url='&YOCTO_DOCS_DEV_URL;#poky'>poky</ulink> term in the Yocto Project | 27 | <ulink url='&YOCTO_DOCS_DEV_URL;#poky'>poky</ulink> term in the Yocto Project |
| 26 | Development Manual. | 28 | Development Manual. |
