2 Yocto Project Supported Architectures And Features
The Yocto Project is putting continuous efforts into testing the changes made to the OpenEmbedded-Core (OE-Core) metadata and core tools. The details on how this test environment functions is described in the Yocto Project Test Environment Manual.
These tests are also run for stable and LTS versions of the Yocto Project. See the Yocto Project Releases and the Stable Release Process section of the Yocto Project Reference Manual for more information on these types of releases.
The infrastructure behind the test environment is the
Yocto Project Autobuilder. The Autobuilder contains a set of Builders that are associated to an
architecture or a feature to test. For example, the qemuarm64 builder
corresponds to testing the ARM 64-bit architecture.
Below is a comprehensive list of target architectures and features that are supported, as well as their level of support. For each architecture or feature, their corresponding builders are also listed.
2.1 Primary Supported
The term “primary” means that dedicated builds for these architectures or features are being run on a daily basis on the Yocto Project Autobuilder and also tested with incoming changes before they merge. These changes are usually on the “-next” Git branches of the OpenEmbedded-Core (OE-Core) repositories.
Below is a list of primary tested features, their maintainer(s) and builder(s):
Feature |
Description |
Maintainer(s) |
Builder(s) |
|---|---|---|---|
ARM architecture testing |
Collective effort |
genericarm64, genericarm64-alt, musl-qemuarm64, qemuarm, qemuarm-alt, qemuarm-oecore, qemuarm-tc, qemuarm64, qemuarm64-alt, qemuarm64-armhost, qemuarm64-ltp, qemuarm64-ptest, qemuarm64-tc, qemuarmv5 |
|
Beaglebone image and SDK build testing |
Collective effort |
beaglebone, beaglebone-alt |
|
reproducibility testing |
Collective effort |
reproducible |
|
Buildtools generation |
Collective effort |
buildtools |
|
meta-agl-core layer testing |
TBD |
meta-agl-core |
|
meta-arm layer testing |
meta-arm mailing list <meta-arm@lists.yoctoproject.org> |
meta-arm |
|
meta-aws layer testing |
TBD |
meta-aws |
|
meta-intel layer testing |
TBD |
meta-intel |
|
meta-exein layer testing |
TBD |
meta-exein |
|
meta-virtualization layer testing |
TBD |
meta-virt |
|
Multilib feature testing |
Collective effort |
multilib |
|
OpenEmbedded-Core layers selftests |
Collective effort |
oe-selftest-fedora, oe-selftest-debian, oe-selftest-armhost |
|
Package managers |
Package managers (RPM, DEB and IPK formats) testing in the
OpenEmbedded Build System (different from the
|
Collective effort |
pkgman-non-rpm (other builders use RPM by default) |
Patchtest tool selftests |
TBD |
patchtest-selftest |
|
RISC-V architecture testing (64-bit) |
Collective effort |
qemuriscv64, qemuriscv64-ptest, qemuriscv64-tc |
|
Systemd init manager testing |
Collective effort |
no-x11, qa-extras2 |
|
Toaster web interface testing |
Collective effort |
toaster |
|
WIC image creation testing |
Collective effort |
wic |
|
X86 architecture testing |
Collective effort |
genericx86, genericx86-64, genericx86-64-alt, genericx86-alt, musl-qemux86, musl-qemux86-64, qemux86, qemux86-64, qemux86-64-alt, qemux86-64-ltp, qemux86-64-ptest, qemux86-64-tc, qemux86-64-x32, qemux86-alt, qemux86-tc, qemux86-world, qemux86-world-alt |
2.2 Secondary Supported
The term “secondary” means that in some cases there is code/feature/support which is desired by people using the project and is in the project’s interests to support, however there isn’t wide enough interest and support to justify testing all incoming changes on it. There are however project member organisations and maintainers willing to run tests and review fixes.
This category may be applicable as support/usage in an area develops and grows, or as support/usage fades but we continue to have tests. It can also apply where resourcing isn’t available for full primary support but there is member/maintainer support for running tests.
We therefore have the following criteria and policies for such items:
It can be clearly isolated and defined by specific configuration.
There is a clear documented group of maintainers agreeing to maintain it.
Those maintainers are active and responsive.
It is being actively and publicly tested (potentially using the Autobuilder by agreement, or otherwise).
Testing would not be part of standard incoming change testing and regressions would not block incoming patches.
The SWAT team would not handle any test builds on the Autobuilder.
Test results can be submitted as part of the release process if desired.
The Yocto Project Technical Steering Committee (TSC) makes decisions on features in this status and Autobuilder testing. Such support would be dropped if the maintainers/testing were inactive.
If you are interested in providing resources for improving testing please contact the Technical Steering Committee (TSC).
Below is a list of secondary tested features, their maintainer(s) and builder(s):
Feature |
Description |
Maintainer(s) |
Builder(s) |
|---|---|---|---|
PowerPC architecture testing (32-bit) |
TBD |
qemuppc, qemuppc-alt, qemuppc-tc |
|
meta-openembedded layer testing |
TBD |
meta-oe |
|
mingw based SDKs testing |
TBD |
meta-mingw |
|
meta-webosose layer testing |
TBD |
meta-webosose |
|
RISC-V architecture testing (32-bit) |
Collective effort |
qemuriscv32, qemuriscv32, qemuriscv32-tc |
2.3 Untested
“Untested” means that whilst the configurations are present in the project, we don’t currently run the tests on any regular basis and new changes are not tested against them. We may take patches in these areas if they make sense but it is on a best effort only basis.
Feature |
Description |
Maintainer(s) |
Builder(s) |
|---|---|---|---|
MIPS architecture testing |
No maintainers |
qemumips, qemumips64, qemumips-alt, qemumips-tc, qemumips64-tc |
|
PowerPC architecture testing (64-bit) |
No maintainers |
qemuppc64, qemuppc64-tc |