Нет описания

Scott Rifenbark ab23dd967e yocto-project-qs and others: Rewrite of the QS 10 лет назад
bitbake 1b88b7426a bitbake: build: Exit scripts with result of last shell function 9 лет назад
documentation ab23dd967e yocto-project-qs and others: Rewrite of the QS 9 лет назад
meta eeb412d01d harfbuzz: upgrade to 1.0.1 9 лет назад
meta-selftest fbfc06a969 recipetool: add appendfile subcommand 10 лет назад
meta-skeleton 203eadfc04 linux-yocto-custom: clarify bbappend versus copy in comments 10 лет назад
meta-yocto 4ab6b46665 qemu: change default version to 4.1 9 лет назад
meta-yocto-bsp 5e357ed88f oe-selftest: restore gummiboot tests 9 лет назад
scripts 67a3807c4c oe-selftest: add scripts/lib and bitbake/lib to path 9 лет назад
.gitignore 3c4c63d0ff gitignore: exclude meta-selftest, drop meta-hob 10 лет назад
.templateconf 614faa66a4 .templateconf: New file for customized template defaults 11 лет назад
LICENSE ef91193c51 Fix license notices for OE-Core 11 лет назад
README bef8558f0e README: expand the Where To Send Patches section 10 лет назад
README.hardware 6fd976f6b4 README.hardware: clarify NFS requirements for edgerouter 10 лет назад
oe-init-build-env 42131b6250 oe-init-build-env: fix for build dirs that have spaces in their path 10 лет назад
oe-init-build-env-memres 61e14ad4eb oe-init-build-env-memres: Fix source check 10 лет назад

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.