| OpenEmbedded | |
|---|---|
 | |
| Developer | 75+ developers[1] |
| Operating system | Linux |
| Platform | Cross-platform |
| Type | Build automation |
| License | MIT |
| Website | www |
| Repository | |
OpenEmbedded (OE) is abuild automationframework andcross-compile environment used to createLinux distributions forembedded devices.[2] The framework is developed by the OpenEmbedded community, which was formally established in 2003. OpenEmbedded is the recommended build system of theYocto Project, which is aLinux Foundation workgroup that assists commercial companies in the development of Linux-based systems for embedded products.
The build system is based onBitBake.[clarification needed] A BitBake configuration file, called a recipe, specifies various information such as dependency and source code locations, how to build a package, and how to install and remove a compiled package. OpenEmbedded tools use these recipes to fetch and patch source code, compile and link binaries, produce binary packages (deb,rpm, ipk), and create bootableimages.
Historically, OpenEmbedded recipes were stored in a single repository, and the metadata was structured as what is now called "OpenEmbedded-Classic". Starting in 2010, the structure was modified to better support the ever-growing number of recipes. Recipe metadata was split into multiple layers. The lowest layer, which includes platform-independent and distribution-independent meta data is called "OpenEmbedded-Core".[3] Architecture-specific, application-specific and distribution-dependent instructions are applied in appropriate target support layers that can override or complement the instructions from lower layers. Additionally, changes to the recipes at the core layer are now managed with a pull model: instead of committing their changes directly to the repository (as was previously the case), developers now send patches to a mailing list. When approved, the patches are merged (pulled) by a maintainer.[3]
The OpenEmbedded framework can be installed and automatically updated viaGit.[2]
The OpenEmbedded Image Creator, called Wic, can be used to generate disk image files, generally with extension.wic.
![[icon]](/mt/?noimg=&dark=on&url=https%3a%2f%2fen.wikipedia.org%2fwiki%2fFile%3aWiki_letter_w_cropped.svg) | This sectionneeds expansion. You can help byadding missing information.(August 2011) |
TheOpenEmbedded Project, created by Chris Larson, Michael Lauer, and Holger Schurig, merged the achievements ofOpenZaurus with contributions from projects likeFamiliar Linux andOpenSIMpad into a common codebase. OpenEmbedded superseded these projects and was used to build any of them from the same code base.
OpenEmbedded-Core (OE-Core) resulted from the merge of theYocto Project with OpenEmbedded.[4] Since then, all package recipes are maintained through OpenEmbedded-Core.
OpenEmbedded-Core has adapted this layered structure in the merge with Yocto and new layer entries were added over time.[5][6] The Layers represent a structure which is only of declarative nature. The specific entries are stricter in the scope of deciding which entry provides which packages. Overview of layers is available in:layers
In OpenEmbedded-Classic, the configurations from Base- to the UI-Layer can be supplemented by variousLinux distributions. The following list is available for OpenEmbedded:
Various devices are supported:[10]
| Linux |
| ||||
|---|---|---|---|---|---|
| XNU | |||||
| QNX | |||||
| Microsoft Windows | |||||
| Zircon | |||||
| FreeBSD,NetBSD | |||||
| HongMeng Kernel | |||||
| FreeRTOS |
| ||||
| Nintendo system software | |||||
| Minix 3 | |||||
| Symbian | |||||
| Others | |||||
| Mobile networks, protocols |
| ||||||
|---|---|---|---|---|---|---|---|
| General operation | |||||||
| Mobile devices |
| ||||||
| Mobile specific software |
| ||||||
| Culture | |||||||
| Environment and health | |||||||
| Law | |||||||
| Linux kernel | |
|---|---|
| Controversies | |
| Distributions | |
| Organizations | |
| Adoption | |
| Media | |
| Security certifications | |
