Nenhuma descrição

Ed Bartosh 4d3bececf6 runqemu: add bindir_native property 8 anos atrás
bitbake bf0fc2da66 bitbake: lib/bb/{data, siggen}: Don't warn on SkipRecipe exceptions 8 anos atrás
documentation 94467d5087 dev-manual, ref-manual: Edits to the "Incrementing Binary Package" section. 8 anos atrás
meta 0637c5ab25 qemu-helper-native: prepare native sysroot for runqemu 8 anos atrás
meta-poky 4c1f654311 poky-world-exclude.inc: add python-pyqt 8 anos atrás
meta-selftest 64a379b325 wic-image-minimal: stop using core-image-minimal 8 anos atrás
meta-skeleton be3c48f607 useradd-example: exclude from world 8 anos atrás
meta-yocto 9d5483c375 meta-yocto: Rename to meta-poky to better match its purpose 9 anos atrás
meta-yocto-bsp a4cca6a131 meta-yocto-bsp: bump to the latest linux stable kernel for the non-x86 BSPs 8 anos atrás
scripts 4d3bececf6 runqemu: add bindir_native property 8 anos atrás
.gitignore 5005cab723 add !meta-poky to .gitignore file 9 anos atrás
.templateconf 9d5483c375 meta-yocto: Rename to meta-poky to better match its purpose 9 anos atrás
LICENSE ef91193c51 Fix license notices for OE-Core 11 anos atrás
README 9d5483c375 meta-yocto: Rename to meta-poky to better match its purpose 9 anos atrás
README.hardware ca4901d834 README.hardware: update MPC8315E-RDB section 8 anos atrás
oe-init-build-env dd5f2f7275 oe-init-build-env*: Make them actually return failures 9 anos atrás
oe-init-build-env-memres dd5f2f7275 oe-init-build-env*: Make them actually return failures 9 anos atrás

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.