Keine Beschreibung

Richard Purdie 5d677d7dba scripts/oe-pkgdata-util: Fix variable name in error handling vor 10 Jahren
bitbake 6e3eefb997 bitbake: toaster: Rework mimetype guessing to fix artifact downloads vor 9 Jahren
documentation bf9e5d6ef6 documentation: Final bits for the 1.8.2 manual set vor 9 Jahren
meta dd90a73c51 xorg-lib: allow native building without x11 DISTRO_FEATURES vor 9 Jahren
meta-selftest a976d63ae5 oe-selftest: add a test for devtool deploy-target vor 10 Jahren
meta-skeleton 6e1ba48120 skeleton: clarify linux-yocto-custom workflow vor 10 Jahren
meta-yocto 3d61b942f7 poky.conf: Bump version for 1.8.2 fido release vor 9 Jahren
meta-yocto-bsp 1726063387 meta-yocto-bsps: remove 3.10 bbappend vor 10 Jahren
scripts 5d677d7dba scripts/oe-pkgdata-util: Fix variable name in error handling vor 9 Jahren
.gitignore 3c4c63d0ff gitignore: exclude meta-selftest, drop meta-hob vor 10 Jahren
.templateconf 614faa66a4 .templateconf: New file for customized template defaults vor 11 Jahren
LICENSE ef91193c51 Fix license notices for OE-Core vor 11 Jahren
README bef8558f0e README: expand the Where To Send Patches section vor 10 Jahren
README.hardware 1e551ec0c3 README.hardware: clarify NFS requirements for edgerouter vor 10 Jahren
oe-init-build-env 61e8fdba04 oe-init-build-env: Improve script sourcing detection. vor 11 Jahren
oe-init-build-env-memres 61e14ad4eb oe-init-build-env-memres: Fix source check vor 10 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-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.