====== Yocto/Openembedded ======

[[https://www.yoctoproject.org/ | yocto]] and [[https://www.openembedded.org/wiki/Main_Page | OpenEmbedded]] provide the tools necessary to create small customised linux distributions aimed at embedded systems.


===== Introduction to Yocto/OpenEmbedded ====

Learn about Yocto and bitbake which uses recipes structured in various layers to  build custom images, see [[introduction|Introduction to Yocto/OpenEmbedded]].

Read about [[layer|Layers]] and [[recipes|Recipes]] therein. 

Use [[devtool]] to add, modify and test new recipes.


===== Getting Started =====

For setting up the build environment, see [[setup|Setup and Building]].

[[ .:getting_started_cpp | Getting Started with Yocto and C/C++]] demonstrates how the build environment is setup, a x86-64 image is built and run on Qemu. Then a C++ application is added to this image.

There are essentially four ways to build on/for a yocto image:

  * Creating a recipe for the application and adding it to the image, see [[ .:getting_started_cpp | Getting Started with Yocto and C/C++]]. This method includes a full build of the image.
  * Crosscompile with a cross development SDK, see [[ .:sdk | SDK]].
  * Use the extensible SDK. With this, you use the regular yocto workflow without the need of building a complete image first, see [[ .:sdks | SDK's]].
  * Include the toolchain in the image and build natively (not recommended), see [[ .:sdks | SDK's]].


===== Our Layers =====

  * [[.:meta-ost | meta-ost ]] is the layer containing recipes required for various OST projects.
  * [[.:meta-ost-ethercat | meta-ost-ethercat ]] is the layer containing recipes for EtherCAT support.


===== Image Download =====
Prebuilt images for our supported platforms together with SDK and extended SDK are available at [[ ..:images/start |Linux Images]].


===== Workflow ======

Learn about how our layers are structured, about how our CI/CD pipeline works and about how you could commit to the project in [[ .:workflow | Structure / Workflow]].


===== ROS =====
Work is under way to include [[ ros | ROS ]] in our builds.