Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Embedded Linux Development with Yocto Project

You're reading from   Embedded Linux Development with Yocto Project Develop fascinating Linux-based projects using the groundbreaking Yocto Project tools

Arrow left icon
Product type Paperback
Published in Jul 2014
Publisher
ISBN-13 9781783282333
Length 142 pages
Edition 1st Edition
Tools
Arrow right icon
Toc

Table of Contents (17) Chapters Close

Preface 1. Meeting the Yocto Project FREE CHAPTER 2. Baking Our Poky-based System 3. Using Hob 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 A. References
Index

Constructing the build directory

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

During the build process, BitBake performs several tasks and 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 modifies the build directory, including a new tarball inside the build/download directory.
  • Source preparation: After the fetching of the source code is complete, it must be prepared for use. This may involve, for example, the unpacking of a tarball or a clone of a local cached Git directory (from the download cache). The source code is prepared in the...
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