Back OpenEmbedded Catalan OpenEmbedded Czech OpenEmbedded German OpenEmbedded French OpenEmbedded Japanese OpenEmbedded Russian OpenEmbedded Turkish OpenEmbedded Chinese
 | |
| Developer(s) | 75+ developers[1] |
|---|---|
| Repository | |
| Operating system | Linux |
| Platform | Cross-platform |
| Type | Build automation |
| License | MIT |
| Website | www |
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. 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 (ipk, deb, rpm), 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.
- ^ "OpenEmbedded Developers". Archived from the original on 2012-11-09.
- ^ a b Brake, Cliff; et al. (2015), "Welcome to OpenEmbedded", OpenEmbedded Wiki, Blacksburg, VA: openembedded.org.
- ^ a b Eggleton, Paul (2015), "OpenEmbedded-Core", OpenEmbedded Wiki, Blacksburg, VA: openembedded.org.