Aucune description

Paul Eggleton 8d315820aa bitbake: runqueue: enable setVariable command to affect task execution il y a 8 ans
bitbake 8d315820aa bitbake: runqueue: enable setVariable command to affect task execution il y a 8 ans
documentation dae00fbb91 sdk-manual: Added note about nullpointer error for launch eclipse il y a 8 ans
meta 252898f56e libpcap: Disable exposed bits of WinPCAP remote capture support il y a 8 ans
meta-poky 18e4688bd5 libc-package.bbclass: split binary localedata even more if asked to il y a 8 ans
meta-selftest 2765231499 recipetool: selftest: Add test for recipetool plugin loading il y a 8 ans
meta-skeleton 7e5b59d7af Remove $COREBASE/LICENSE from LIC_FILES_CHKSUM il y a 8 ans
meta-yocto 9d5483c375 meta-yocto: Rename to meta-poky to better match its purpose il y a 9 ans
meta-yocto-bsp 209a19ce16 edgerouter.conf: enable generation of wic.bmap il y a 8 ans
scripts a5438f8f74 oe-buildenv-internal: show usage output il y a 8 ans
.gitignore 5005cab723 add !meta-poky to .gitignore file il y a 9 ans
.templateconf 9d5483c375 meta-yocto: Rename to meta-poky to better match its purpose il y a 9 ans
LICENSE ef91193c51 Fix license notices for OE-Core il y a 11 ans
README 9d5483c375 meta-yocto: Rename to meta-poky to better match its purpose il y a 9 ans
README.hardware 9ba7226744 README.hardware: minor update to edgerouter section il y a 8 ans
oe-init-build-env dd5f2f7275 oe-init-build-env*: Make them actually return failures il y a 9 ans
oe-init-build-env-memres dd5f2f7275 oe-init-build-env*: Make them actually return failures il y a 9 ans

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.