Go to file
Richard Purdie 5424fc6186 lttng-tools: Disable slow tests to fix ptest runs
Add a patch disabling some ptests in lttng-tools since they are slow, give
no output on the console and cause the ptest run to error due to our 450s
inactivity timeout.

(From OE-Core rev: 328d5c9a1dcfa4c636fd6d6e05f2474c15dc9f7a)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2025-08-19 11:48:50 +01:00
bitbake bitbake: fetch2/git: verify if local clone contains tag 2025-08-19 11:35:52 +01:00
contrib contrib/git-hooks: add a sendemail-validate example hook that adds FROM: lines to outgoing patch emails 2020-12-30 14:01:07 +00:00
documentation poky.yaml.in: increase required disk space to 140G 2025-08-08 23:41:11 +01:00
meta lttng-tools: Disable slow tests to fix ptest runs 2025-08-19 11:48:50 +01:00
meta-poky poky: remove Ubuntu 20.04 from supported distribtions 2025-08-08 16:14:52 +01:00
meta-selftest selftest/devtool: add devtool upgrade selftest for recipes with git submodules 2025-08-14 10:31:10 +01:00
meta-skeleton layer.conf: Update to whinlatter release series 2025-06-20 13:07:15 +01:00
meta-yocto-bsp genericarm64/genericx86-64/heabglebone-yocto: Default to zstd compressed image output 2025-08-06 22:33:00 +01:00
scripts bootimg_pcbios: add help and usage comments 2025-08-14 10:31:11 +01:00
.b4-config b4-config: Add basic support for b4 contribution workflow 2025-02-06 10:40:55 +00:00
.gitignore vscode: drop .vscode folder 2024-02-19 11:34:33 +00:00
.templateconf meta-poky/conf: move default templates to conf/templates/default/ 2022-09-01 10:07:02 +01:00
LICENSE meta/lib+scripts: Convert to SPDX license headers 2019-05-09 16:31:55 +01:00
LICENSE.GPL-2.0-only
LICENSE.MIT meta/lib+scripts: Convert to SPDX license headers 2019-05-09 16:31:55 +01:00
MAINTAINERS.md MAINTAINERS.md: fix markdown style issues 2025-02-05 12:49:56 +00:00
MEMORIAM MEMORIAM: Add recognition for contributors no longer with us 2020-01-30 15:22:35 +00:00
oe-init-build-env oe-init-build-env: generate .vscode from template 2024-02-19 11:34:33 +00:00
README.hardware.md README: Move to using markdown as the format 2021-06-16 16:33:18 +01:00
README.md Add README link to README.poky 2021-07-19 18:07:21 +01:00
README.OE-Core.md README.OE-Core.md: fix markdown style issues 2025-02-05 12:49:56 +00:00
README.poky.md README: Move to using markdown as the format 2021-06-16 16:33:18 +01:00
README.qemu.md README.qemu.md: fix markdown style issues 2025-02-05 12:49:56 +00:00
SECURITY.md SECURITY.md: fix markdown style issues 2025-02-05 12:49:56 +00:00

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