Go to file
Ross Burton 3ca2b7ea9f libnsl2: set CVE_PRODUCT
Our libnsl2 recipe is just libnsl version 2.x, so set the CVE vendor and
product pair appropriately as per:

https://www.cvedetails.com/version/1177013/Libnsl-Project-Libnsl-2.0.0.html

(From OE-Core rev: c8e9cde342e935b309aeab06029fc5a46ef89028)

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit d0e77d3f9217b96f1c77ba65fc9b8420f413c401)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
2025-02-12 06:29:33 -08:00
bitbake bitbake: cooker: Make cooker 'skiplist' per-multiconfig/mc 2025-02-12 06:29:33 -08:00
contrib
documentation dev-manual/building: document the initramfs-framework recipe 2025-01-29 06:20:44 -08:00
meta libnsl2: set CVE_PRODUCT 2025-02-12 06:29:33 -08:00
meta-poky poky.conf: bump version for 5.1.2 2025-01-13 05:49:08 -08:00
meta-selftest oeqa/selftest/bbclasses: Add tests for systemd and update-rc.d interaction 2024-09-01 11:05:20 +01:00
meta-skeleton useradd-example: Fix S = WORKDIR reference 2024-05-23 11:26:39 +01:00
meta-yocto-bsp layer.conf: Update to styhead 2024-09-06 18:39:44 +01:00
scripts devtool: ide-sdk remove the plugin from eSDK installer 2025-02-03 06:24:37 -08: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: fix patchtest entry 2024-06-25 11:50:58 +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