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

Tracking image, package, and SDK contents


The easiest way to ensure we have the image, packages, and SDK, along with the expected contents, is to use the Build History mechanism.

When a recipe is updated for a new version or has its code changed, it may influence the contents put in the generated packages and, as a consequence, in the image or SDK.

As Poky deals with a huge amount of recipes, and our images or SDKs frequently have tens or hundreds of packages included, it may be quite difficult to track the package contents. The Poky tool responsible for helping us in this task is the Build History.

The Build History, as we can guess from its name, keeps a history of the contents of several artifacts built during the use of Poky. It can track package, image, and SDK building.

To enable the Build History in our system, we need to add the following lines of code in our build/conf/local.conf file:

INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "1"

The INHERIT method includes the buildhistory class...