generic-poky

OpenEmbedded "poky" with some sysmocom specific modifications. Mostly used only up to sysmocom release 201310, but the "pyro" branch is still used for 201705

Go to file

Richard Purdie 2000698b17 meta-yocto: Split into distro and bsp components Now we have settled on best practises and compliance criteria, bring meta-yocto into compliance by separating out the hardware support components into meta-yocto-bsp leaving policy configuration in meta-yocto. Also rename the meta-yocto scripts directory to OE-Core can be a clearly isolated component in poky. (From meta-yocto rev: eac90e27a032ea23d9a4f35c7eef8b1940c80e22) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>		2012-09-05 17:32:15 +01:00
bitbake	bitbake: taskdata: Don't add dependencies on tasks that don't exist	2012-08-30 17:44:07 -07:00
documentation	yocto-docs/.gitignore: Final fix to ignore mega-manual.	2012-09-04 12:55:03 +01:00
meta	classes/qmake_base: support linux-gnuspe/linux-uclibcspe TARGET_OS	2012-09-05 17:32:14 +01:00
meta-hob	meta-hob: Add a new meta-hob layer	2012-02-24 00:39:10 +00:00
meta-skeleton	linux-yocto-custom: Clarify usage and clear COMPATIBLE_MACHINE	2012-08-07 12:56:34 +01:00
meta-yocto	meta-yocto: Split into distro and bsp components	2012-09-05 17:32:15 +01:00
meta-yocto-bsp	meta-yocto: Split into distro and bsp components	2012-09-05 17:32:15 +01:00
scripts	scripts/cleanup-workdir: change autoconf-nativesdk to nativesdk-autoconf	2012-09-04 18:03:18 +01:00
.gitignore	gitignore: ignore build*/ entirely	2012-06-21 13:03:04 +01:00
LICENSE	LICENSE: Clarify the license recipe source code is under	2010-06-10 10:13:18 +01:00
README	README: Clarify where to send patches	2012-08-22 14:05:00 +01:00
README.hardware	README.hardware: extend USB-ZIP instructions	2012-04-01 12:52:03 +01:00
oe-init-build-env	Various typoes fixed, all comments or output strings.	2012-03-26 12:13:05 +01:00

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 = "") 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, patches against the various components
should be sent to their respective upstreams.

bitbake:
    bitbake-devel@lists.openembedded.org

meta-yocto:
    poky@yoctoproject.org

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