Go to file
Kristi Rifenbark 81498aac95 yocto-project-qs: Updated Next Steps list
Updated manual descriptions to fit current
manual structures.

(From yocto-docs rev: 81d8add49fd09deef432d9a0cc08c9f380c671ed)

Signed-off-by: Kristi Rifenbark <kristi.rifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-07-12 00:28:16 +01:00
bitbake bitbake: knotty: Drop task prefix of PLAIN log messages 2017-07-08 13:29:54 +01:00
documentation yocto-project-qs: Updated Next Steps list 2017-07-12 00:28:16 +01:00
meta libiconv: remove 0001-Fix-link-error-when-compiling-with-gcc-O0.patch 2017-07-11 15:57:08 +01:00
meta-poky local.conf.sample: drop image-swab reference 2017-07-06 15:03:10 +01:00
meta-selftest selftest/seltest.py: Add test to check imports from other layers 2017-06-28 20:55:08 +01:00
meta-skeleton meta*: Add LAYERSERIES_COMPAT and LAYERSERIES_CORENAMES markup to layer.conf 2017-06-12 15:08:30 +01:00
meta-yocto/conf meta-yocto: Rename to meta-poky to better match its purpose 2016-02-28 11:31:17 +00:00
meta-yocto-bsp oeqa/selftest/systemdboot: Add Test to check boot file is created correctly 2017-06-23 14:13:59 +01:00
scripts linux-yocto-custom: include a user feature description file 2017-07-06 15:03:10 +01:00
.gitignore add !meta-poky to .gitignore file 2016-03-26 08:06:58 +00:00
.templateconf meta-yocto: Rename to meta-poky to better match its purpose 2016-02-28 11:31:17 +00:00
LICENSE Fix license notices for OE-Core 2014-01-02 12:58:54 +00:00
oe-init-build-env oe-init-build-env*: Make them actually return failures 2016-03-20 23:12:30 +00:00
oe-init-build-env-memres oe-init-build-env-memres: swap parameter order 2017-06-28 15:52:17 +01:00
README meta-yocto: Rename to meta-poky to better match its purpose 2016-02-28 11:31:17 +00:00
README.hardware README.hardware: update flashing instructions for MPC8315 2017-06-09 17:13:45 +01:00
README.LSB README.LSB: describe oe-core's deviations from the LSB spec 2017-06-28 15:52:17 +01:00

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 (built using a tool called combo-layer),
patches against the various components should be sent to their respective
upstreams:

bitbake:
    Git repository: http://git.openembedded.org/bitbake/
    Mailing list: bitbake-devel@lists.openembedded.org

documentation:
    Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
    Mailing list: yocto@yoctoproject.org

meta-poky, meta-yocto-bsp:
    Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto(-bsp)
    Mailing list: poky@yoctoproject.org

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.

    Git repository: http://git.openembedded.org/openembedded-core/
    Mailing list: 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.