User:Scientist.St/OpenEmbedded

OpenEmbedded is a software framework to create Linux distributions aimed for, but not restricted to, embedded devices. The Build system is based on BitBake reci

User:Scientist.St/OpenEmbedded
OpenEmbedded
Developerabove 75 developers[1].
Operating systemLinux
PlatformCross-platform
TypeBuild automation
LicenseMIT
Websitewww.openembedded.org

Overview

OpenEmbedded is a software framework to create Linux distributions aimed for, but not restricted to, embedded devices. The Build system is based on BitBake reciepes[2], wich behave similar to Gentoo's ebuilds.

Reciepes in the old OpenEmbedded-Classic where all found in one place, in the new OpenEmbedded-Core the structure has changed into meta layers[3][4] to make it easier to add custom recipes.

OpenEmbedded can be installed and automatically updated via Git[2]

OpenEmbedded-Classic

The OpenEmbedded Project (OE for short, but mostly called OE-dev, following the name of the mailing list[5]) was created by Chris Larson, Michael Lauer, and Holger Schurig, merging 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. Stable maintenance builds exist for the old OpenEmbedded-Classic[6], altough the most development is, or will be based, on the new OpenEmbedded-Core in the future.

OpenEmbedded-Core

The OpenEmbedded-Core Project (OE-Core for short) resulted from the merge of the Yocto Project™ with OpenEmbedded.[7] This is the most recent version of OpenEmbedded and many of the OE-dev recipes are available in OE-Core. Newer versions of package recipes may only get ported for OpenEmbedded-Core

Layer organisation in OpenEmbedded-Core

OpenEmbedded-Core has adapted this layered structure in the merge with Yocto and new layer entries were added over time.[3][4]

The Layers represent a structure which is only of declarative nature. The specific entries are more strict in the scope of deciding which entry provides wich packages.

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

  • meta-efikamx (Efika devices)
  • meta-intel (Intel embedded devices)
  • meta-nslu2 (NSLU2 devices)
  • meta-openpandora (Openpandora device layer)
  • meta-smartphone (various smartphone devices)
  • meta-texasinstruments (Texas Instruments devices)
  • meta-xilinx (Xilinx devices)
  • (Others)

Yocto layer

OpenEmbedded-Core layer

  • openembedded-core
  • meta-openembedded

Distributions supported by OpenEmbedded

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

Supported hardware

See [10] for a partial list of supported devices.

Boards and processors

The BeagleBoard and Gumstix[11][12] boards from Texas Instruments and several I.MX devices (for example the I.MX28 series[13]) from Freescale are supported.[citation needed]

Other well known boards like the PandaBoard are also supported [14][15] along with other hardware.

Some devices of the IBM PowerPC series are supported by OpenEmbedded [16]

Smartphones

Smartphones like the Nokia N800 and Neo FreeRunner are supported.

Porting OpenEmbedded to new hardware

The constellation of OpenEmbedded, especially the open design, allows it to get OpenEmbedded to adapt new hardware fairly easy.[17][18]

See also

Original source: [19]

References

  1. ^ OpenEmbedded developers
  2. ^ a b Official website
  3. ^ a b c Yocto & OpenEmbedded Core Layers
  4. ^ a b c OpenEmbedded Core Layer Index
  5. ^ OpenEmbedded mailing list
  6. ^ Maintenance branch
  7. ^ a b c Linux Foundation Yocto Project and Openembedded merged
  8. ^ SHR Project
  9. ^ Ben Combee on Palm Developer Forum - Fri Jul 16, 2010. Building static libs
  10. ^ Overview of OpenEmbedded supported machines
  11. ^ Using OpenEmbedded build system for Gumstix
  12. ^ TI Gumstix OpenEmbedded development environment
  13. ^ Unofficial OpenEmbedded I.MX28 support
  14. ^ OMAPpedia Pandaboard info
  15. ^ OMAPpedia Angstrom Openembedded setup
  16. ^ Power.org devcon 07 OpenEmbedded presentation
  17. ^ Yocto Project Bord Support Package guide
  18. ^ Poky handbook porting to new machines guide
  19. ^ OpenEmbedded Success Stories
  20. ^ Poky handbook


Category:Embedded Linux Category:Build automation Category:Personal digital assistant software Category:Software using the MIT license

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.