Book Image

Embedded Linux Development using Yocto Projects - Second Edition

By : Otavio Salvador, Daiane Angolini
Book Image

Embedded Linux Development using Yocto Projects - Second Edition

By: Otavio Salvador, Daiane Angolini

Overview of this book

Yocto Project is turning out to be the best integration framework for creating reliable embedded Linux projects. It has the edge over other frameworks because of its features such as less development time and improved reliability and robustness. Embedded Linux Development using Yocto Project starts with an in-depth explanation of all Yocto Project tools, to help you perform different Linux-based tasks. The book then moves on to in-depth explanations of Poky and BitBake. It also includes some practical use cases for building a Linux subsystem project using Yocto Project tools available for embedded Linux. The book also covers topics such as SDK, recipetool, and others. By the end of the book, you will have learned how to generate and run an image for real hardware boards and will have gained hands-on experience at building efficient Linux systems using Yocto Project.
Table of Contents (22 chapters)
Title Page
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
7
Diving into BitBake Metadata
Index

Detailing the layer's source code


Usually, a layer has a directory tree, as shown in the following screenshot:

The layer name should start with meta-; it is not a requirement, but the advised naming convention. Inside this directory, there are two files, <layer>/COPYING and <layer>/README, a license, and a message to the user. In <layer>/README, we must specify any other dependency and information that the layer's users need to know.

The classes folder should hold both the classes provided the classes that are specific to that layer (the .bbclass files). It is an optional directory.

The <layer>/conffolderis mandatory and should provide the configuration files (the.conffiles). Primarily, the layer configuration file<layer>/conf/layer.conf, to be detailed in the next chapter, is the file with the layer definition.

When the <layer>/conf folder is from a BSP layer, the directory structure should look like the following screenshot:

If the <layer>/conf folder...