Yocto Project

The Yocto Project has the aim and objective of attempting to improve the lives of developers of customized Linux systems supporting the ARM, MIPS, PowerPC and x86/x86-64 architectures. A key part of this is the OpenEmbedded build system, which enables developers to create their own Linux distribution specific to their environment. The Yocto Project and OpenEmbedded Project share maintainership of the main parts of the OpenEmbedded build system: the build engine, BitBake, and the core metadata, OpenEmbedded-Core. The Yocto Project provides a reference implementation called Poky, which contains the OpenEmbedded build system plus a large set of recipes, arranged in a hierarchical system of layers, that can be used as a fully functional template for a customized embedded operating system.

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.

The project offers different sized targets from "tiny" to fully featured images which are configurable and customisable by the end user. 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.

As well as building Linux systems, there is also an ability to generate a toolchain for cross compilation and a software development kit (SDK) tailored to their own distribution. The project tries to be software and vendor agnostic. Thus, for example, it is possible to select which package manager format to use (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 is known for making good documentation a priority and 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.^[4]

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 administrative and technical 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 Project 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.

Major releases occur about every 6 months (April and October).^[9]

Version 3.1 was the first long-term support (LTS) release.^[10] 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.^[11]

Since version 3.1, the release codenames are names of mountains or passes in the Cumbria county in Northern England.^{[12][circular reference]}

The Yocto Project Branding Program provides an opportunity to associate the value of using the Yocto Project with a company or product. The Yocto Project Branding Program defines steps to register organizations as Yocto Project Participants, and content as Yocto Project Compatible. Yocto Project Participant is appropriate for organizations who use and support the Yocto Project publicly. Yocto Project Compatible is appropriate for products, BSPs, and other OE-compatible layers, and related open-source projects, and is open to Yocto Project member organizations.^[14]

• Buildroot
• T2 SDE

• Official website
• Deciding between Buildroot and Yocto, LWN.net, April 6, 2016, by Nathan Willis