No Description

Richard Purdie 6271fcb589 bitbake: bitbake-worker: Handle SIGKILL of parent gracefully 10 years ago
bitbake 6271fcb589 bitbake: bitbake-worker: Handle SIGKILL of parent gracefully 10 years ago
documentation 798fc18ef7 ref-manual: New description for KERNEL_CLASSES variable. 10 years ago
meta dae69e6dcf ptest: use fakeroot for do_install_ptest_base 10 years ago
meta-selftest 8be95c5fbe devtool: add upgrade feature 10 years ago
meta-skeleton 0f425669b7 service: tweak example recipe 10 years ago
meta-yocto db8886de9a distro/include: Move files to OE-Core for support distrodata 10 years ago
meta-yocto-bsp 6b17c38318 linux-yocto-3.14: Update to latest revisions 10 years ago
scripts 69b7a613fc devtool: fix running from a different directory 10 years ago
.gitignore f169733738 bitbake: toaster tests: gitignore and use absolute path for log file 10 years ago
.templateconf 614faa66a4 .templateconf: New file for customized template defaults 11 years ago
LICENSE ef91193c51 Fix license notices for OE-Core 11 years ago
README bef8558f0e README: expand the Where To Send Patches section 10 years ago
README.hardware 790b2293d2 README.hardware: drop mention of binary-only drivers 10 years ago
oe-init-build-env 42131b6250 oe-init-build-env: fix for build dirs that have spaces in their path 10 years ago
oe-init-build-env-memres 61e14ad4eb oe-init-build-env-memres: Fix source check 10 years ago

README

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-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.