Bez popisu

Richard Purdie 68aefbb27d bitbake: bitbake-worker: Ensure pipe closure doesn't crash before killpg() před 10 roky
bitbake 68aefbb27d bitbake: bitbake-worker: Ensure pipe closure doesn't crash before killpg() před 10 roky
documentation 798fc18ef7 ref-manual: New description for KERNEL_CLASSES variable. před 10 roky
meta 58ef81c5cc testimage: Handle core-image-lsb-sdk qemumips test restriction před 10 roky
meta-selftest 8be95c5fbe devtool: add upgrade feature před 10 roky
meta-skeleton 0f425669b7 service: tweak example recipe před 10 roky
meta-yocto db8886de9a distro/include: Move files to OE-Core for support distrodata před 10 roky
meta-yocto-bsp d4585fa23d bsps: update 3.14 SRCREVs před 10 roky
scripts 06cde90f9f devtool: update-recipe: get srcuri parameters with decodeurl() před 10 roky
.gitignore f169733738 bitbake: toaster tests: gitignore and use absolute path for log file před 10 roky
.templateconf 614faa66a4 .templateconf: New file for customized template defaults před 11 roky
LICENSE ef91193c51 Fix license notices for OE-Core před 11 roky
README bef8558f0e README: expand the Where To Send Patches section před 10 roky
README.hardware 790b2293d2 README.hardware: drop mention of binary-only drivers před 10 roky
oe-init-build-env 42131b6250 oe-init-build-env: fix for build dirs that have spaces in their path před 10 roky
oe-init-build-env-memres 61e14ad4eb oe-init-build-env-memres: Fix source check před 10 roky

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.