Go to file
Alexander Kanavin 2db3a58bc7 systemtap: correctly set include location for the python module
This issue was as well exposed by setting S to be in UNPACKDIR.

(From OE-Core rev: a9b8cd548bc4f12b7aa28209d7c04181c95b7e7a)

Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2025-06-12 11:03:43 +01:00
bitbake bitbake: doc: update releases.rst 2025-06-12 09:56:42 +01:00
contrib
documentation docs: remove lz4 from required packages 2025-06-06 22:22:43 +01:00
meta systemtap: correctly set include location for the python module 2025-06-12 11:03:43 +01:00
meta-poky templates/default: do not separately enable sdl in qemu-system-native 2025-06-09 17:43:42 +01:00
meta-selftest oe-selftest: add new ext dtb recipe 2025-06-05 11:02:21 +01:00
meta-skeleton
meta-yocto-bsp genericx86*: allow higher tunes 2025-05-22 23:38:49 +01:00
scripts scripts/scriptutils: silence warning about S not existing in emptysrc 2025-06-05 11:02:22 +01:00
.b4-config
.gitignore
.templateconf
LICENSE
LICENSE.GPL-2.0-only
LICENSE.MIT
MAINTAINERS.md
MEMORIAM
oe-init-build-env
README.hardware.md
README.md
README.OE-Core.md
README.poky.md
README.qemu.md
SECURITY.md

Poky

Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for 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 BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.

As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.

The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/

OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.

Contribution Guidelines

Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.

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:

OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):

BitBake (files in bitbake/):

Documentation (files in documentation/):

meta-yocto (files in meta-poky/, meta-yocto-bsp/):

If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.

CII Best Practices