OpenEmbedded

OpenEmbedded (OE) is a build automation framework and cross-compile environment used to create Linux distributions for embedded devices.

Uses your system voice; voice and rate in settings.

≈ 10 min read

Cite, export and learn8 citation formats · 8 exports · lesson and quiz

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

OpenEmbedded (OE) is a build automation framework and cross-compile environment used to create Linux distributions for embedded devices.[2] The framework is developed by the OpenEmbedded community, which was formally established in 2003. OpenEmbedded is the recommended build system of the Yocto Project, which is a Linux Foundation workgroup that assists commercial companies in the development of Linux-based systems for embedded products.

The build system is based on BitBake.[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 bootable images.

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 via Git.[2]

The OpenEmbedded Image Creator, called Wic, can be used to generate disk image files, generally with extension .wic.

History

edit edit source

The OpenEmbedded Project, created by Chris Larson, Michael Lauer, and Holger Schurig, merged the achievements of OpenZaurus with contributions from projects like Familiar Linux and OpenSIMpad 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 the Yocto Project with OpenEmbedded.[4] Since then, all package recipes are maintained through OpenEmbedded-Core.

OpenEmbedded-Core (OE-Core) contains a core set of metadata, including base recipes and classes used by OpenEmbedded and related systems.[5] In this structure, developers can extend the build system without modifying the core metadata, with different layers supporting specific hardware platforms and software configurations.[6]

The BitBake build tool, developed alongside OpenEmbedded, serves as the task execution engine and manages package builds and dependencies.[7]

Layer organisation

edit edit source

OpenEmbedded-Core has adapted this layered structure in the merge with Yocto and new layer entries were added over time.[8][9] 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.openembedded.org/layerindex/branch/master/layers/

Developer layer
The user-defined layer for custom Bitbake recipes. Embedded system software developers would place their recipe here if the software would not fit the commercial or base layer.
Commercial layer
Packages, plugins, and configurations from open source vendors go in this layer.
UI-specific layer
Layers currently present within the meta-openembedded layer:
  • meta-efl (Enlightenment window manager)
  • meta-gnome (GNOME window manager)
  • meta-gpe (GPE window manager)
  • meta-xfce (Xfce window manager)
Hardware-specific layer
Yocto layer
  • meta-yocto (Yocto Project layer[8][4])
OpenEmbedded-Core layer
  • openembedded-core
  • meta-openembedded

Distributions supported

edit edit source

In OpenEmbedded-Classic, the configurations from Base- to the UI-Layer can be supplemented by various Linux distributions. The following list is available for OpenEmbedded:

Supported hardware

edit edit source

Various devices are supported:[13]

Boards and processors
The BeagleBoard from Texas Instruments, and a variety of devices based on an ARM CPU are supported.
Smartphones
Smartphones like the Nokia N800 and Neo FreeRunner are supported.
Porting to new hardware
The constellation of OpenEmbedded, especially the open design, allows it to get OpenEmbedded to adapt new hardware fairly easy.[14][improper synthesis?][15][improper synthesis?]

Software development kits

edit edit source

The OpenEmbedded build system can generate software development kits(SDKs) for developing applications for target devices. These include a cross-compilation toolchain and libraries and headers matched to the target system. The extensible SDK additionally includes devtool, which supports adding applications and libraries, modifying existing components, and testing changes on target hardware.[16]

See also

edit edit source

References

edit edit source
  1. ^ "OpenEmbedded Developers". Archived from the original on 2012-11-09. Wikipedia revision 1377890514, retrieved 2026-11-21
  2. ^ a b Brake, Cliff; et al. (2015), "Welcome to OpenEmbedded", OpenEmbedded Wiki, Blacksburg, VA: openembedded.org. Wikipedia revision 1377890514, retrieved 2026-11-21
  3. ^ a b Eggleton, Paul (2015), "OpenEmbedded-Core", OpenEmbedded Wiki, Blacksburg, VA: openembedded.org. Wikipedia revision 1377890514, retrieved 2026-11-21
  4. ^ a b "Yocto Project Aligns Technology with OpenEmbedded and Gains Corporate Collaborators". Archived from the original on 2012-01-11. Wikipedia revision 1377890514, retrieved 2026-11-21
  5. ^ "OpenEmbedded-Core - Openembedded.org". www.openembedded.org. Retrieved 2026-04-19. Wikipedia revision 1377890514, retrieved 2026-11-21
  6. ^ "Yocto Project Overview and Concepts Manual — The Yocto Project ® 5.3-tip documentation". docs.yoctoproject.org. Retrieved 2026-04-19. Wikipedia revision 1377890514, retrieved 2026-11-21
  7. ^ "BitBake User Manual — Bitbake 2.16 documentation". docs.yoctoproject.org. Retrieved 2026-04-19. Wikipedia revision 1377890514, retrieved 2026-11-21
  8. ^ a b Yocto & OpenEmbedded Core Layers Archived 2011-09-19 at the Wayback Machine Wikipedia revision 1377890514, retrieved 2026-11-21
  9. ^ "OpenEmbedded Metadata Index - layers". Archived from the original on 2013-06-22. Retrieved 2013-06-18. Wikipedia revision 1377890514, retrieved 2026-11-21
  10. ^ "SHR". Archived from the original on 2011-10-07. Retrieved 2011-09-30. Wikipedia revision 1377890514, retrieved 2026-11-21
  11. ^ Ben Combee on Palm Developer Forum - Fri Jul 16, 2010. Building static libs Archived 2011-07-26 at the Wayback Machine Wikipedia revision 1377890514, retrieved 2026-11-21
  12. ^ "B2C Info Solutions". Wikipedia revision 1377890514, retrieved 2026-11-21
  13. ^ "Overview of OE supported machines". Retrieved 2022-09-08. Wikipedia revision 1377890514, retrieved 2026-11-21
  14. ^ Yocto Project Board Support Package guide Wikipedia revision 1377890514, retrieved 2026-11-21
  15. ^ "Yocto Project Development Manual". Archived from the original on 2021-01-16. Retrieved 2011-11-28. Wikipedia revision 1377890514, retrieved 2026-11-21
  16. ^ "Introduction — Yocto Project ® Application Development and the Extensible Software Development Kit (eSDK)". docs.yoctoproject.org. Retrieved 2026-10-01. Wikipedia revision 1377890514, retrieved 2026-11-21
edit edit source Mobile operating systems Linux XNU QNX Microsoft
Windows
Zircon FreeBSD, NetBSD HongMeng Kernel
  • Defunct: EMUI (non GMS-based)
  • LiteOS
  • Huawei Band OS
FreeRTOS
  • Amazfit OS
    • Zepp OS
  • MIUI Band OS
Nintendo
system software Minix 3 Symbian NuttX Others Mobile phonesMobile
networks
,
protocols General
operation Mobile
devices
Mobile
specific
software Culture Environment
and health Law LinuxLinux kernel Controversies Distributions Organizations Adoption Media Security
certifications
Software in the Public InterestProjects People

Text derived from https://en.wikipedia.org/w/index.php?oldid=1377890514 under CC BY-SA 4.0; modifications have been made.

Words in each sectionLayer organisationLayer organisationLayer organisation: 205 words205HistoryHistoryHistory: 145 words145Supported hardwareSupported hardwareSupported hardware: 78 words78Software development ki…Software development kitsSoftware development kits: 57 words57See alsoSee alsoSee also: 53 words53Distributions supportedDistributions supportedDistributions supported: 44 words44
Words in each section. Measured from the stored article body; sections below the minimum are not plotted.

References

  1. ↩Wikipedia “OpenEmbedded” revision 1377890514 · retrieved 2026-10-20 date of establishment (×1) · confidence 0.95 revision URL

Provenance

snapshot enwiki-001377890514 · captured 2026-10-01 · ledger · version history

Cite this page as: encyclopegia.org, “OpenEmbedded”, snapshot enwiki-001377890514. https://encyclopegia.org/a/openembedded