No Description

Richard Purdie 69d985c0c3 bitbake: fetch2: Change git fetcher not to destroy old references 4 years ago
bitbake 69d985c0c3 bitbake: fetch2: Change git fetcher not to destroy old references 4 years ago
documentation 2535349363 poky.ent: Updated the release date to July 2018. 6 years ago
meta 9b7bc41dfa build-appliance-image: Update to pyro head revision 7 years ago
meta-poky ebb42af282 poky: Update version to 2.3.4 7 years ago
meta-selftest 64a379b325 wic-image-minimal: stop using core-image-minimal 8 years ago
meta-skeleton be3c48f607 useradd-example: exclude from world 8 years ago
meta-yocto 9d5483c375 meta-yocto: Rename to meta-poky to better match its purpose 9 years ago
meta-yocto-bsp e9834ba34b linux-yocto/4.1: generix86* bsp fix perf issue with gcc >=7 7 years ago
scripts 8689313447 scripts/test-dependencies.sh: remove 7 years ago
.gitignore 5005cab723 add !meta-poky to .gitignore file 9 years ago
.templateconf 9d5483c375 meta-yocto: Rename to meta-poky to better match its purpose 9 years ago
LICENSE ef91193c51 Fix license notices for OE-Core 11 years ago
README 9d5483c375 meta-yocto: Rename to meta-poky to better match its purpose 9 years ago
README.hardware ca4901d834 README.hardware: update MPC8315E-RDB section 8 years ago
oe-init-build-env dd5f2f7275 oe-init-build-env*: Make them actually return failures 9 years ago
oe-init-build-env-memres dd5f2f7275 oe-init-build-env*: Make them actually return failures 9 years ago

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.