Keine Beschreibung

brian avery 9bc41e1e8d bitbake: toaster: remove cut and paste cruft vor 8 Jahren
bitbake 9bc41e1e8d bitbake: toaster: remove cut and paste cruft vor 8 Jahren
documentation aa7e2717d3 ref-manual: remove core-image-directfb reference vor 8 Jahren
meta 47ee6c2153 selftest/wic: Add tests for --exclude-dir option. vor 8 Jahren
meta-poky e8b1864f70 poky.conf: prune SANITY_TESTED_DISTROS vor 8 Jahren
meta-selftest 03648d3d04 m4: use wildcard for selftest bbappend vor 8 Jahren
meta-skeleton be3c48f607 useradd-example: exclude from world vor 8 Jahren
meta-yocto 9d5483c375 meta-yocto: Rename to meta-poky to better match its purpose vor 9 Jahren
meta-yocto-bsp 3b93282a59 linux-yocto: Update genericx86* SRCREVs for linux-yocto 4.9 vor 8 Jahren
scripts 01b9ab89de wic: direct: move creation of PartitionedImage to __init__ vor 8 Jahren
.gitignore 5005cab723 add !meta-poky to .gitignore file vor 9 Jahren
.templateconf 9d5483c375 meta-yocto: Rename to meta-poky to better match its purpose vor 9 Jahren
LICENSE ef91193c51 Fix license notices for OE-Core vor 11 Jahren
README 9d5483c375 meta-yocto: Rename to meta-poky to better match its purpose vor 9 Jahren
README.hardware ca4901d834 README.hardware: update MPC8315E-RDB section vor 8 Jahren
oe-init-build-env dd5f2f7275 oe-init-build-env*: Make them actually return failures vor 9 Jahren
oe-init-build-env-memres dd5f2f7275 oe-init-build-env*: Make them actually return failures vor 9 Jahren

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