Difference between revisions of "Yocto Project"

From eLinux.org
Jump to: navigation, search
(Overview)
(Getting Started)
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
== Overview ==
 
== Overview ==
The Yocto Project is an project that intends to provide an OpenSource build system, based on top of Poky and [[Open Embedded]], that enables developers to create their own linux distribution specific to their environment.  
+
The Yocto Project is a project attempting to improve the lives of developers of customised Linux systems by focusing on having one set of great tools rather than the several sets of mediocre ones that existed when the project was founded. A key part of this is an OpenSource build system based around the [[Open Embedded]] architecture that enables developers to create their own linux distribution specific to their environment. This reference implementation of [[Open Embedded]] is called [[Poky]]
To ease this even further, Yocto offers some templates of different sizes (tiny to fullblown), which the developer can adapt (extend or shrink) by the simple means of editing some configuration files.
+
  
Internally Yocto uses bitbake recipes which are quite similar to Gentoo's ebuild system, so adding new packages or modifying packages is quite easy.
+
There are several other subprojects under the project umbrella which include Eglibc, pseudo, cross-prelink, eclipse integration ADT/SDK, the matchbox suite of applications and many others.
  
When Yocto is then run, it takes care of fetching the sources, compiling, packaging and creating the image, but also provides the developer with a toolchain for cross compilation and a Application Developer Kit (ADK) tailored to his own distribution.
+
Through OpenEmbedded-Core included as part of Poky, the Yocto Project offers some templates of different sizes (tiny to fullblown), which the developer can adapt (extend or shrink) by the simple means of editing some configuration files. A tool called "bitbake" is used to perform builds and the instructions for the build are called "recipes". This is similar to Gentoo's ebuild system, so adding new packages or modifying packages is quite easy. When bitbake is then run, it takes care of fetching the sources, compiling, packaging and creating the image, but also provides the developer with a toolchain for cross compilation and a Software Developer Kit (SDK) tailored to his own distribution (also referred to as the Application Developer Toolkit (ADT). Depending on the configuration, the created image can then be deployed directly onto the target hardware or emulated via [[qemu]]. Other code such as bootloaders and firmware can optionally be compiled.
Depending on the configuration, the created image can then be deployed directly onto the target hardware or emulated via [[qemu]].
+
  
Unfortunately Yocto currently leaves out the [[bootloader]] part of the system, "as this should be provided by the board vendor".
+
A quick overview of Yocto's internal flow can be found here: [http://www.yoctoproject.org/docs/current/yocto-project-qs/figures/yocto-environment.png Yocto Flow (Getting Started Guide) ]
  
A quick overview of Yocto's internal flow can be found here: [[ http://www.yoctoproject.org/docs/current/yocto-project-qs/figures/yocto-environment.png Yocto Flow (Getting Started Guide) ]]
+
The Yocto Project supports x86, x86_64, [[ARM]], [[PowerPC]] and MIPS targets.
  
It currently supports x86, x86_64, [[ARM]], [[PowerPC]] and MIPS.
+
The project works closely with the upstream projects, both in keeping up with the latest software releases but also ensuring patches such as those for cross compiling are contributed back. The kernel is updated at least once every 6 months for regular releases, but also providing the possibility to run the latest git version of the kernel - and tries to be software and vendor agnostic - thus you can e.g. choose which package manager format you intend to use in your embedded linux distribution (deb, rpm, ipk).  
 
+
Yocto intends to work closely with the upstream projects - e.g. updating the kernel at least once every 6 months for regular releases, but also providing the possibility to run the latest git version of the kernel - and tries to be software and vendor agnostic - thus you can e.g. choose which package manager format you intend to use in your embedded linux distribution (deb, rpm, ipkg).  
+
  
 
Yocto has also an excellent integration into the Eclipse IDE, and allows you to do most of the necessary steps from within Eclipse.
 
Yocto has also an excellent integration into the Eclipse IDE, and allows you to do most of the necessary steps from within Eclipse.
Line 21: Line 17:
  
 
[http://www.yoctoproject.org/documentation/getting-started Getting Started (from the project website)]
 
[http://www.yoctoproject.org/documentation/getting-started Getting Started (from the project website)]
 +
 +
Another resource is Robert Day's crash course for building yocto for the BeagleBoard.  See:
 +
http://www.crashcourse.ca/wiki/index.php/Yocto_Project_Quick_Start
 +
 +
== FAQs ==
 +
Here are various FAQs about the Yocto project:
 +
 +
* http://www.crashcourse.ca/wiki/index.php/Yocto_FAQ
 +
** Robert Day's FAQ based on question's he's gotten about the Yocto Project
 +
* https://wiki.yoctoproject.org/wiki/How_do_I
 +
** this has a few technical items
 +
* http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#faq
 +
** Poky is one sample distribution provided by the Yocto Project, and so understanding how Poky is built and be customized is a good start to understanding Yocto.
 +
* https://wiki.yoctoproject.org/wiki/FAQ
 +
** this has overview stuff, not of a technical nature (reading it will likely just confuse you)
 +
 +
Finally, here is my own (Tim Bird's) introduction and overview:
 +
* [[Yocto Project Introduction]]
  
 
== History ==
 
== History ==
Line 26: Line 40:
 
[http://www.embeddedlinuxconference.com/elc_europe10/index.html Embedded Linux Conference Europe 2010]
 
[http://www.embeddedlinuxconference.com/elc_europe10/index.html Embedded Linux Conference Europe 2010]
  
 +
* Version 0.9 was released Oct 2012 at ELCE 2010
 
* Version 1.0 was released on April 6, 2011.
 
* Version 1.0 was released on April 6, 2011.
 
* Version 1.1 was released on 21 Oct 2011 and was presented during the ELCE 2011
 
* Version 1.1 was released on 21 Oct 2011 and was presented during the ELCE 2011
 
+
* Version 1.2 was released in April 30, 2012
* Yocto is sponsored by the Linux Foundation.
+
* Version 1.3 is anticipated on 26 Oct 2012
* Yocto technology derives from Poky Linux, which was a branch of [[Open Embedded]]
+
 
+
  
 
== Talks ==
 
== Talks ==

Latest revision as of 18:59, 20 November 2012

Overview

The Yocto Project is a project attempting to improve the lives of developers of customised Linux systems by focusing on having one set of great tools rather than the several sets of mediocre ones that existed when the project was founded. A key part of this is an OpenSource build system based around the Open Embedded architecture that enables developers to create their own linux distribution specific to their environment. This reference implementation of Open Embedded is called Poky

There are several other subprojects under the project umbrella which include Eglibc, pseudo, cross-prelink, eclipse integration ADT/SDK, the matchbox suite of applications and many others.

Through OpenEmbedded-Core included as part of Poky, the Yocto Project offers some templates of different sizes (tiny to fullblown), which the developer can adapt (extend or shrink) by the simple means of editing some configuration files. A tool called "bitbake" is used to perform builds and the instructions for the build are called "recipes". This is similar to Gentoo's ebuild system, so adding new packages or modifying packages is quite easy. When bitbake is then run, it takes care of fetching the sources, compiling, packaging and creating the image, but also provides the developer with a toolchain for cross compilation and a Software Developer Kit (SDK) tailored to his own distribution (also referred to as the Application Developer Toolkit (ADT). Depending on the configuration, the created image can then be deployed directly onto the target hardware or emulated via qemu. Other code such as bootloaders and firmware can optionally be compiled.

A quick overview of Yocto's internal flow can be found here: Yocto Flow (Getting Started Guide)

The Yocto Project supports x86, x86_64, ARM, PowerPC and MIPS targets.

The project works closely with the upstream projects, both in keeping up with the latest software releases but also ensuring patches such as those for cross compiling are contributed back. The kernel is updated at least once every 6 months for regular releases, but also providing the possibility to run the latest git version of the kernel - and tries to be software and vendor agnostic - thus you can e.g. choose which package manager format you intend to use in your embedded linux distribution (deb, rpm, ipk).

Yocto has also an excellent integration into the Eclipse IDE, and allows you to do most of the necessary steps from within Eclipse.

Getting Started

Getting Started (from the project website)

Another resource is Robert Day's crash course for building yocto for the BeagleBoard. See: http://www.crashcourse.ca/wiki/index.php/Yocto_Project_Quick_Start

FAQs

Here are various FAQs about the Yocto project:

Finally, here is my own (Tim Bird's) introduction and overview:

History

  • The Linux Foundation announced the Yocto Project in October, 2010 at

Embedded Linux Conference Europe 2010

  • Version 0.9 was released Oct 2012 at ELCE 2010
  • Version 1.0 was released on April 6, 2011.
  • Version 1.1 was released on 21 Oct 2011 and was presented during the ELCE 2011
  • Version 1.2 was released in April 30, 2012
  • Version 1.3 is anticipated on 26 Oct 2012

Talks