Book Image

Yocto for Raspberry Pi

By : TEXIER Pierre-Jean, Petter Mabäcker
Book Image

Yocto for Raspberry Pi

By: TEXIER Pierre-Jean, Petter Mabäcker

Overview of this book

The Yocto Project is a Linux Foundation workgroup, which produces tools (SDK) and processes (configuration, compilation, installation) that will enable the creation of Linux distributions for embedded software, independent of the architecture of embedded software (Raspberry Pi, i.MX6, and so on). It is a powerful build system that allows you to master your personal or professional development. This book presents you with the configuration of the Yocto Framework for the Raspberry Pi, allowing you to create amazing and innovative projects using the Yocto/ OpenEmbedded eco-system. It starts with the basic introduction of Yocto's build system, and takes you through the setup and deployment steps for Yocto. It then helps you to develop an understanding of Bitbake (the task scheduler), and learn how to create a basic recipe through a GPIO application example. You can then explore the different types of Yocto recipe elements (LICENSE, FILES, SRC_URI, and so on). Next, you will learn how to customize existing recipes in Yocto/OE layers and add layers to your custom environment (qt5 for example).
Table of Contents (18 chapters)
Yocto for Raspberry Pi
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
3
Mastering Baking with Hob and Toaster

Introducing layers


A layer is just a collection of recipes and/or configuration that can be used on top of Yocto/OE-Core.

The advantage of using an environment such as Yocto/OE (the Poky reference system) comes from the fact that this project handles a lot of metadata (definition files (.conf) of the machine (Raspberry Pi), classes, and recipes (.bb)) that covers everything from simple applications (gpio-packt) to graphics applications such as OpenGLES, EFL, or Qt.

The main motivation of using layers is to organize the long list of providers better and still make sure users may be able to pick only the required or desired provider. It is also a way of providing customizable source code that can be used for any architecture or modified in the way the user needs.

The other advantage is that we can choose all the layers required for each project (from the most basic to the most complex). We can modify them to be consistent with our architecture (ARM for the Raspberry Pi), but a layer can be reused...