Yocto Background and Yocto Term

1. Source of Yocto
It started with the Sharp Zaurus SL-5000 series, a Linux-based PDA announced in 2001.

OpenZaurus project
- Sharp announced the source code of the ROM Image of SL-5000 products in accordance with the open source license, and based on this(announced the source code), the OpenZaurus project started in 2002.

The project(Using a debian-based source build method) has shown limitations in supporting multiple target architectures as the project expands in size.

OpenEmbedded was launched in 2003 to improve this problem.
 

2. OpenEmbedded project
- Packages in OpenZaurus have been integrated into this project.

OpenEmbedded is divided into a Python build program called BitBake and a build specification called Metadata(setting files related to recipe).

Bitbake was separated into an independent project like Make Tool(Cmake, …) in 2004.

Therefore, it was separated as follows:

- Bitbake: Separate independent projects

- OpenEmbedded : A project to manage Metadata for Bitbake

OpenEmbedded has grown rapidly, supporting 7,000 recipe and 300 machines.

In the case of OpenEmbedded, as it operates as a "Push model" that is committed by developers, it is not easy to manage conflicts in code as the scale grows, and commercial support is not easy.

There have been various attempts to improve this, and Poky Linux has appeared as one of them.
 

3. Poky Linux
Poky Linux, released in 2006 by a startup called OpenedHand, is a project that neatly organizes existing OpenEmbedded.

- Features
Has about 800 selected recipes
Supports virtualization software virtual environments(QEMU) and SDK builds.
Has a very well-organized manual

The company was merged with Intel in 2008, and Poky focuses only on Atom-based equipment.
 

4. Yocto Project and Feature
Projects to improve the Embedded Linux Distribution development process based on Poky Linux (released in 2010 by Linux Foundation Workgroup)
OE-Core: Metadata separated from Poky in 2011. OpenEmbedded, which is currently referred to in Yocto, refers to OE-Core.
OE-Classic: Previous OpenEmbedded

Feature
- OE-Core

    Supports major architectures such as ARM, x86, x86-64, MIPS, and MIPS64, ....

    Support X-Based GUI with QEMU emulated machine. (Real hardware X)

- Metadata sets that are not hardware dependent are supported.
- Separate BSP metadata with Bitbake's Layering function.
- The software modules are divided into separate layering such as meta-qt, meta-nodejs, etc.
- There is no possibility of project collision by managing poky and openembeded, with a Pull model(not push model which is directly committed by developers).
 

5. Yocto Term
bitbake : "Build tool" separated from OE-Classic 2004
OE-Core (OpenEmbedded-Core) : Core Metadata separated from Poky in 2011. provides meta-openembedded.
OE-Classic (formerly OpenEmbedded) : Bitbake and OE-Core
Poky : Metadata and Bitbake to create an integrated image with OE-Core
Yocto Project : Embedded Linux Foundation Workgroup managed Embedded Linux Distribution Building System
Metadata : configuration file (*.conf), class file (*.bbclass), recipe file (*.bb, *.bbappend)
 

#Source of Yocto #Yocto #BitBake #Poky #Feature #Term