You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Ross Burton 1bff3fc86f oe-init-build-env-memres: use shell instead of Python to show the port number 8 years ago
bitbake bitbake: bitbake: Update to version 1.20.0 8 years ago
documentation dev-manual: Updated Git repo path for eclipse plugins. 8 years ago
meta pseudo: warn twice if the 32-bit toolchain appears broken 8 years ago
meta-hob meta-*/conf/layer.conf: tweak BBFILES comment 9 years ago
meta-skeleton hello-mod: Add comment for kernel module package naming 8 years ago
meta-yocto poky: Update to 1.5 release version 8 years ago
meta-yocto-bsp beagleboard: update the dts location 8 years ago
scripts runqemu: Use correct kvm CPU options for qemux86* with kvm 8 years ago
.gitignore gitignore: only ignore meta- directories 9 years ago
LICENSE LICENSE: Clarify the license recipe source code is under 12 years ago
README README: Clarify where to send patches 9 years ago
README.hardware README.hardware: Replace atom-pc with genericx86 8 years ago
oe-init-build-env oe-init-build-env: Make it use the correct $OEROOT with zsh 9 years ago
oe-init-build-env-memres oe-init-build-env-memres: use shell instead of Python to show the port number 8 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 = "") 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.