Brak opisu

Mariano Lopez 835525c8bb runqemu-ifup: Check if the tap interface is set up correctly 9 lat temu
bitbake a9053ac082 bitbake: toaster: Add tests for error message display on the build dashboard 9 lat temu
documentation 7d30d67b26 ref-manual: Updated the allarch class description. 9 lat temu
meta b13c0be4b0 qemurunner: Show the output of runqemu script 9 lat temu
meta-selftest e191120581 oeqa/selftest: verify that devtool can use plugins in other layers 9 lat temu
meta-skeleton 59668f2a03 linux-yocto-custom: fix typo in Upstream-Status tag 9 lat temu
meta-yocto d9528d9a39 toasterconf: update meta-yocto to jethro and drop dizzy 9 lat temu
meta-yocto-bsp ceeb52a254 linux-yocto: Update SRCREV for genericx86* BSPs 9 lat temu
scripts 835525c8bb runqemu-ifup: Check if the tap interface is set up correctly 9 lat temu
.gitignore f169733738 bitbake: toaster tests: gitignore and use absolute path for log file 9 lat temu
.templateconf 614faa66a4 .templateconf: New file for customized template defaults 11 lat temu
LICENSE ef91193c51 Fix license notices for OE-Core 11 lat temu
README bef8558f0e README: expand the Where To Send Patches section 10 lat temu
README.hardware 790b2293d2 README.hardware: drop mention of binary-only drivers 9 lat temu
oe-init-build-env 42131b6250 oe-init-build-env: fix for build dirs that have spaces in their path 10 lat temu
oe-init-build-env-memres 61e14ad4eb oe-init-build-env-memres: Fix source check 10 lat temu

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.