Go to file
Deepesh Varatharajan 588bba19dc rust-target-config: Fix ABI override for powerpc64le target
Ensure the powerpc64le check is exclusive by using `elif`, preventing the
powerpc64 condition from overriding it. This keeps the ABI as elfv2 for
PPC64LE and fixes related build failures.

(From OE-Core rev: 1d4067329d0b84f94aaf2f63d282bb9c99ba5557)

Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2025-10-30 11:06:28 +00:00
bitbake bitbake: bitbake/doc: Correct name of bitbake-dumpsig 2025-10-17 16:43:20 +01:00
contrib
documentation migration-guides/release-notes-5.3: updates 2025-10-29 23:16:34 +00:00
meta rust-target-config: Fix ABI override for powerpc64le target 2025-10-30 11:06:28 +00:00
meta-poky poky: Update SANITY_TESTED_DISTROS 2025-10-01 15:17:37 +01:00
meta-selftest oeqa/bblayers.py: add tests for adding new built-in fragments 2025-10-01 10:52:54 +01:00
meta-skeleton meta-skeleton: fix spaces in assignment 2025-09-22 22:09:48 +01:00
meta-yocto-bsp parselogs-ignores-genericarm64.txt: add Qualcomm rb3gen2 workarounds 2025-10-13 23:29:52 +01:00
scripts wic: add wic tests and support setting GPT diskid 2025-10-30 11:06:28 +00: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
LICENSE
LICENSE.GPL-2.0-only
LICENSE.MIT
MAINTAINERS.md MAINTAINERS.md: fix markdown style issues 2025-02-05 12:49:56 +00: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.md
README.OE-Core.md README.OE-Core.md: fix markdown style issues 2025-02-05 12:49:56 +00:00
README.poky.md
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