Yocto Project
Page Module:Message box/ambox.css has no content.
This article needs additional citations for verification. (April 2016) |
Page Module:Infobox/styles.css has no content.
| Yocto Project | |
|---|---|
| Lua error in package.lua at line 80: module 'Module:InfoboxImage/data' not found. | |
| Initial release | 2010 |
| Written in | Primarily Python, Shell |
| Website | Script error: No such module "WikidataIB". |
Script error: No such module "Check for conflicting parameters".
The Yocto Project is a Linux Foundation collaborative open source project whose goal is to produce tools and processes that enable the creation of Linux distributions for embedded and IoT software that are independent of the host hardware architecture, supports customization and results in repeatable output. The toolset managed by the project, commonly called yocto, consists of interoperable tools, metadata, and processes. The project was announced by the Linux Foundation in 2010 and launched in March, 2011, in collaboration with 22 organizations, including OpenEmbedded.[2]
The Yocto and OpenEmbedded projects share maintenance of BitBake (build engine) and OpenEmbedded-Core (core metadata). Yocto provides a reference implementation called Poky, which contains the OpenEmbedded build system plus a large set of recipes, arranged in hierarchical layers, that can be used as a template for a customized, embedded operating system.
In addition to building a Linux system, yocto provides other, related features. It can generate a toolchain for cross compilation and a software development kit (SDK) tailored to a hardware environment. It supports package creation in a variety of formats including deb, rpm, or ipk. Within builds, there are options for various build-time sanity/regression tests, and also the option to boot and test certain images under QEMU to validate the build.
The project encourages interaction with upstream projects and has contributed heavily to OpenEmbedded-Core and BitBake as well as to numerous upstream projects, including the Linux kernel.[3] The resulting images are typically useful in systems where embedded Linux would be used, these being single-use focused systems or systems without the usual screens/input devices associated with desktop Linux systems.
There are several other sub-projects under the project umbrella which include CROPS, pseudo, the matchbox suite of applications, and many others. One of the central goals of the project is interoperability among these tools.
In October 2018, Arm Holdings partnered with Intel in order to share code for embedded systems through the Yocto Project.[4]
Governance
The Yocto Project is one of many collaborative projects organized as a non-profit under the banner of the Linux Foundation.[5] The project's governance is divided loosely into technical and administrative arms, although many members participate in both camps.
At a technical level, the project is overseen by the project architect Richard Purdie (a Linux Foundation Fellow[6]) who has a long history of involvement with many of the project's components and technologies.[7] The architect maintains a hierarchy of maintainers for the different components of the system, much as the Linux kernel is maintained.
The administrative arm consists of an advisory board made up of representatives from the project's member organizations, including several major silicon vendors, commercial operating system vendors that use yocto as their upstream, corporate users, as well as representatives from groups such as software consultants and community members.[8] The member organizations of this board provide resources to the project. There are also several advisory board working groups that handle administrative functions for the project such as finance, infrastructure, advocacy and outreach, and community management.
Branding program
The Yocto Project Branding Program provides an opportunity to associate the use of the Yocto Project with an organization or product. An organization that uses yocto is a candidate to be branded as a Yocto Project Participant. A product (such as a BSP or any OE-compatible layer) is a candidate to be branded as Yocto Project Compatible.[9]
Releases
Major releases occur about every 6 months (April and October).[10] Version 3.1 was the first long-term support (LTS) release.[11] Since then, a new LTS release is added every two years. The 3.1 series and 4.0 were originally planned for two years but extended to four. The next LTS releases are planned for 4 years.[12] Since version 3.1, the release codenames are names of mountains or passes in the Cumbria county in Northern England.
The project attempts to update documentation for each release, retaining all documents for current and archived releases on the website, as the documentation can change significantly with any release.[13]
| Release[14][15] | Codename | Date | Support |
|---|---|---|---|
| 6.0 (LTS)Page Template:Version/styles.css has no content. | Wrynose | 04/2026 | 04/2030 |
| 5.3Page Template:Version/styles.css has no content. | Whinlatter | 12/2025 | EOL |
| 5.2Page Template:Version/styles.css has no content. | Walnascar | 04/2025 | EOL |
| 5.1Page Template:Version/styles.css has no content. | Styhead | 10/2024 | EOL |
| 5.0 (LTS)Page Template:Version/styles.css has no content. | Scarthgap | 04/2024 | 04/2028 |
| 4.3Page Template:Version/styles.css has no content. | Nanbield | 11/2023 | EOL |
| 4.2Page Template:Version/styles.css has no content. | Mickledore | 05/2023 | EOL |
| 4.1Page Template:Version/styles.css has no content. | Langdale | 10/2022 | EOL |
| 4.0 (LTS)Page Template:Version/styles.css has no content. | Kirkstone | 05/2022 | EOL |
| 3.4Page Template:Version/styles.css has no content. | Honister | 11/2021 | EOL |
| 3.3Page Template:Version/styles.css has no content. | Hardknott | 04/2021 | EOL |
| 3.2Page Template:Version/styles.css has no content. | Gatesgarth | 11/2020 | EOL |
| 3.1 (LTS)Page Template:Version/styles.css has no content. | Dunfell | 04/2020 | EOL |
| 3.0Page Template:Version/styles.css has no content. | Zeus | 10/2019 | EOL |
| 2.7Page Template:Version/styles.css has no content. | Warrior | 04/2019 | EOL |
| 2.6Page Template:Version/styles.css has no content. | Thud | 11/2018 | EOL |
| 2.5Page Template:Version/styles.css has no content. | Sumo | 04/2018 | EOL |
| 2.4Page Template:Version/styles.css has no content. | Rocko | 10/2017 | EOL |
| 2.3Page Template:Version/styles.css has no content. | Pyro | 04/2017 | EOL |
| 2.2Page Template:Version/styles.css has no content. | Morty | 10/2016 | EOL |
| 2.1Page Template:Version/styles.css has no content. | Krogoth | 04/2016 | EOL |
| 2.0Page Template:Version/styles.css has no content. | Jethro | 10/2015 | EOL |
| 1.8Page Template:Version/styles.css has no content. | Fido | 04/2015 | EOL |
| 1.7Page Template:Version/styles.css has no content. | Dizzy | 10/2014 | EOL |
| 1.6Page Template:Version/styles.css has no content. | Daisy | 04/2014 | EOL |
| 1.5Page Template:Version/styles.css has no content. | Dora | 10/2013 | EOL |
| 1.4Page Template:Version/styles.css has no content. | Dylan | 04/2013 | EOL |
| 1.3Page Template:Version/styles.css has no content. | Danny | 10/2012 | EOL |
| 1.2Page Template:Version/styles.css has no content. | Denzil | 04/2012 | EOL |
| 1.1Page Template:Version/styles.css has no content. | Edison | 10/2011 | EOL |
| 1.0Page Template:Version/styles.css has no content. | Bernard | 2011 | EOL |
| 0.9Page Template:Version/styles.css has no content. | Laverne | 2010 | EOL |
Legend: Unsupported Supported Latest version Preview version Future version | |||
See also
References
Page Template:Reflist/styles.css has no content.
- ^ Release notes for 5.3 (whinlatter)
- ^ Page Module:Citation/CS1/styles.css has no content."The Linux Foundation Announces Yocto Project Steering Group and Release 1.0".
- ^ Page Module:Citation/CS1/styles.css has no content."Yocto Project Linux Kernel Development Manual". docs.yoctoproject.org. Retrieved 2021-04-21.
- ^ Page Module:Citation/CS1/styles.css has no content."Arm cozies up to Intel for second time in a week – this time to borrow tools from Yocto Project for Mbed Linux". The Register.
- ^ Page Module:Citation/CS1/styles.css has no content."Projects - The Linux Foundation". The Linux Foundation. Retrieved 2018-01-05.
- ^ Page Module:Citation/CS1/styles.css has no content."Linux Foundation Fellows - The Linux Foundation". The Linux Foundation. Retrieved 2022-09-08.
- ^ Page Module:Citation/CS1/styles.css has no content."Technical Leadership | Yocto Project". www.yoctoproject.org. Archived from the original on 2018-01-05. Retrieved 2018-01-05.
- ^ Page Module:Citation/CS1/styles.css has no content."Members – Yocto Project". www.yoctoproject.org. Retrieved 2018-07-31.
- ^ Page Module:Citation/CS1/styles.css has no content."Branding Program – Yocto Project". www.yoctoproject.org. Archived from the original on 2018-07-31. Retrieved 2018-07-31.
- ^ Page Module:Citation/CS1/styles.css has no content."Releases - Yocto Project". wiki.yoctoproject.org. Retrieved 2018-07-31.
- ^ Page Module:Citation/CS1/styles.css has no content."Yocto Project Long Term Support Announced". 26 February 2020.
- ^ Page Module:Citation/CS1/styles.css has no content."Releases - Yocto Project".
- ^ Page Module:Citation/CS1/styles.css has no content."Yocto Project Documentation". docs.yoctoproject.org. Retrieved 2021-04-21.
- ^ Yocto Project Release Activity
- ^ yoctoproject: Releases
External links
- Deciding between Buildroot and Yocto, LWN.net, April 6, 2016, by Nathan Willis
Lua error in package.lua at line 80: module 'Module:Navbox/configuration' not found. Template:Linux Foundation Lua error in package.lua at line 80: module 'Module:Navbox/configuration' not found. Lua error in package.lua at line 80: module 'Module:Navbox/configuration' not found. Template:Embedded systems