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.
If BBSERVER is set, we should unset it before proceeding. Its assumed the user will have unloaded the server from memory should they have wished to do so. (From OE-Core rev:
|8 years ago|
|bitbake||8 years ago|
|documentation||8 years ago|
|meta||8 years ago|
|meta-hob||8 years ago|
|meta-skeleton||8 years ago|
|meta-yocto||8 years ago|
|meta-yocto-bsp||8 years ago|
|scripts||8 years ago|
|.gitignore||9 years ago|
|LICENSE||11 years ago|
|README||9 years ago|
|README.hardware||8 years ago|
|oe-init-build-env||8 years ago|
|oe-init-build-env-memres||8 years ago|
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:
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:
Where to Send Patches
As Poky is an integration repository, patches against the various components
should be sent to their respective upstreams.
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
Note: The scripts directory should be treated with extra care as it is a mix
of oe-core and poky-specific files.