Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Advanced Search Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Embedded Linux Development using Yocto Projects
  • Table Of Contents Toc
  • Feedback & Rating feedback
Embedded Linux Development using Yocto Projects

Embedded Linux Development using Yocto Projects

By : Otavio Salvador, Angolini
3.4 (5)
Buy this Book
close
close
Embedded Linux Development using Yocto Projects

Embedded Linux Development using Yocto Projects

3.4 (5)
By: Otavio Salvador, Angolini
Buy this Book

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 (15 chapters)
close
close
close
Preface
Icon
Preface
Icon
What this book covers
Icon
What you need for this book  
Icon
Who this book is for
Icon
Conventions
Icon
Customer support
Free Chapter
1
Meeting the Yocto Project
Icon
Meeting the Yocto Project
Icon
What is the Yocto Project?
Icon
Delineating the Yocto Project
Icon
Understanding Poky
Icon
Using BitBake
Icon
OpenEmbedded-Core
Icon
Metadata
Icon
The alliance of the OpenEmbedded Project and the Yocto Project
Icon
Summary
2
Baking Our Poky-Based System
Icon
Baking Our Poky-Based System
Icon
Configuring a host system
Icon
Downloading the Poky source code
Icon
Preparing the build environment
Icon
Knowing the local.conf file
Icon
Building a target image
Icon
Running images in QEMU
Icon
Summary
3
Using Toaster to Bake an Image
Icon
Using Toaster to Bake an Image
Icon
What is Toaster?
Icon
Installing Toaster
Icon
Starting Toaster
Icon
Building an image to QEMU
Icon
Summary
4
Grasping the BitBake Tool
Icon
Grasping the BitBake Tool
Icon
Understanding the BitBake tool
Icon
Exploring metadata
Icon
Parsing metadata
Icon
Dependencies
Icon
Preferring and providing recipes
Icon
Fetching the source code
Icon
Understanding BitBake's tasks
Icon
Generating a root filesystem image
Icon
Summary
5
Detailing the Temporary Build Directory
Icon
Detailing the Temporary Build Directory
Icon
Detailing the build directory
Icon
Constructing the build directory
Icon
Exploring the temporary build directory
Icon
Understanding the work directory
Icon
Understanding the sysroot directories
Icon
Summary
6
Assimilating Packaging Support
Icon
Assimilating Packaging Support
Icon
Using supported package formats
Icon
Understanding shared state cache
Icon
Explaining package versioning
Icon
Specifying runtime package dependencies
Icon
Package feeds
Icon
Summary
7
Diving into BitBake Metadata
Icon
Diving into BitBake Metadata
Icon
Using metadata
Icon
Summary
8
Developing with the Yocto Project
Icon
Developing with the Yocto Project
Icon
Deciphering the software development kit
Icon
Working with the Poky SDK
Icon
Integrating with Eclipse
Icon
Summary
9
Debugging with the Yocto Project
chevron up
Icon
Debugging with the Yocto Project
Icon
Differentiating metadata and application debugging
Icon
Tracking image, package, and SDK contents
Icon
Debugging packaging
Icon
Logging information during task execution
Icon
Utilizing a development shell
Icon
Using the GNU Project Debugger for debugging
Icon
Summary
10
Exploring External Layers
Icon
Exploring External Layers
Icon
Powering flexibility with layers
Icon
Detailing the layer's source code
Icon
Adding meta layers
Icon
The Yocto Project layer ecosystem
Icon
Summary
11
Creating Custom Layers
Icon
Creating Custom Layers
Icon
Making a new layer
Icon
Adding metadata to the layer
Icon
Creating an image
Icon
Adding a package recipe
Icon
Adding support to a new machine definition
Icon
Using a custom distribution
Icon
MACHINE_FEATURES versus DISTRO_FEATURES
Icon
Understanding the variables scope
Icon
Summary
12
Customizing Existing Recipes
Icon
Customizing Existing Recipes
Icon
Common use cases
Icon
Adding extra options to recipes based on Autoconf
Icon
Applying a patch
Icon
Adding extra files to the existing packages
Icon
Changing recipe feature configuration
Icon
Customizing BusyBox
Icon
Customizing the linux-yocto framework
Icon
Summary
13
Achieving GPL Compliance
Icon
Achieving GPL Compliance
Icon
Understanding copyleft
Icon
Managing software licensing with Poky
Icon
Using Poky to achieve copyleft compliance
Icon
Summary
14
Booting Our Custom Embedded Linux
Icon
Booting Our Custom Embedded Linux
Icon
Exploring the boards
Icon
Discovering the right BSP layer
Icon
Baking for the hardware
Icon
Booting our baked image
Icon
Next steps
Icon
Summary

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

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
Start a 7-day FREE trial
End of Section 1
Next Section

Create a Note

Modal Close icon
You need to login to use this feature.
notes
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Delete Note

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Edit Note

Modal Close icon
Write a note (max 255 characters)
Cancel
Update Note

Confirmation

Modal Close icon
claim successful
Order Page Read Now

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY