Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Yocto for Raspberry Pi

You're reading from   Yocto for Raspberry Pi Create unique and amazing projects by using the powerful combination of Yocto and Raspberry Pi

Arrow left icon
Product type Paperback
Published in Jun 2016
Publisher Packt
ISBN-13 9781785281952
Length 214 pages
Edition 1st Edition
Concepts
Arrow right icon
Authors (2):
Arrow left icon
TEXIER Pierre-Jean TEXIER Pierre-Jean
Author Profile Icon TEXIER Pierre-Jean
TEXIER Pierre-Jean
Petter Mabäcker Petter Mabäcker
Author Profile Icon Petter Mabäcker
Petter Mabäcker
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Meeting the Yocto Project FREE CHAPTER 2. Building our First Poky Image for the Raspberry Pi 3. Mastering Baking with Hob and Toaster 4. Understanding BitBake 5. Creating, Developing, and Deploying on the Raspberry Pi 6. Working with External Layers 7. Deploying a Custom Layer on the Raspberry Pi 8. Diving into the Raspberry Pi's Peripherals and Yocto Recipes 9. Making a Media Hub on the Raspberry Pi 10. Playing with an LCD Touchscreen and the Linux Kernel 11. Contributing to the Raspberry Pi BSP Layer 12. Home Automation Project - Booting a Custom Image

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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image