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
Embedded Linux Development using Yocto Projects

You're reading from   Embedded Linux Development using Yocto Projects Learn to leverage the power of Yocto Project to build efficient Linux-based products

Arrow left icon
Product type Paperback
Published in Nov 2017
Publisher
ISBN-13 9781788470469
Length 162 pages
Edition 2nd Edition
Tools
Arrow right icon
Authors (2):
Arrow left icon
Otavio Salvador Otavio Salvador
Author Profile Icon Otavio Salvador
Otavio Salvador
Daiane Angolini Daiane Angolini
Author Profile Icon Daiane Angolini
Daiane Angolini
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Meeting the Yocto Project FREE CHAPTER 2. Baking Our Poky-Based System 3. Using Toaster to Bake an Image 4. Grasping the BitBake Tool 5. Detailing the Temporary Build Directory 6. Assimilating Packaging Support 7. Diving into BitBake Metadata 8. Developing with the Yocto Project 9. Debugging with the Yocto Project 10. Exploring External Layers 11. Creating Custom Layers 12. Customizing Existing Recipes 13. Achieving GPL Compliance 14. Booting Our Custom Embedded Linux

Constructing the build directory

Poky's inputs and outputs were already detailed at a high level of abstract in the previous chapters. We already know that BitBake uses metadata to generate different types of artifacts, including images. Besides the generated artifacts, BitBake creates much more content during this process, which may be used in several ways, dependent upon our goals.

During the build process, BitBake performs several tasks and continuously modifies the build directory. We can understand it better following the usual BitBake flow, as follows:

  • Fetching: The first action realized by BitBake is to download the source code. This step may modify the build directory as it tries to use the cached downloaded copy of the source code, or performs the download and stores it inside the build/download directory.
  • Source preparation: After fetching the source code is complete...
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