Go to file
Archana Polampalli 0c4e028627 go: fix CVE-2025-58185
Parsing a maliciously crafted DER payload could allocate large amounts of memory,
causing memory exhaustion.

(From OE-Core rev: f27acc863ee34b56e2c49dc96ad2b58fb35e2d46)

Signed-off-by: Archana Polampalli <archana.polampalli@windriver.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
2025-11-14 06:45:29 -08:00
bitbake bitbake: fetch2/wget: Keep query parameters in URL during checkstatus 2025-11-14 06:45:29 -08:00
contrib
documentation ref-manual/classes.rst: document the relative_symlinks class 2025-11-03 07:17:02 -08:00
meta go: fix CVE-2025-58185 2025-11-14 06:45:29 -08:00
meta-poky poky.conf: bump version for 5.0.13 2025-10-13 12:46:28 -07:00
meta-selftest pulseaudio: Add audio group explicitly 2025-09-09 09:08:09 -07:00
meta-skeleton linux-yocto-custom: Fix comment override syntax 2024-07-03 06:28:36 -07:00
meta-yocto-bsp yocto-bsp/genericarm64: add virtio-gpu 2024-04-08 23:33:53 +01:00
scripts scripts/install-buildtools: Update to 5.0.12 2025-10-13 12:42:58 -07: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
LICENSE.GPL-2.0-only
LICENSE.MIT
MAINTAINERS.md MAINTAINERS.md: no more need for a prelink-cross maintainer 2022-05-07 22:31:21 +01:00
MEMORIAM
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: fix mail address in git example command 2023-09-04 10:27:46 +01:00
README.poky.md README: Move to using markdown as the format 2021-06-16 16:33:18 +01:00
README.qemu.md README.OE-Core/README.qemu: Move to markdown format 2021-07-20 08:51:06 +01:00
SECURITY.md SECURITY.md: add file 2023-10-19 11:31:13 +01: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