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

Understanding the work directory


The build/tmp/work directory is split by architecture. For example, when working with the machine qemuarm, we have the following four directories:

  • all-poky-linux

  • armv5te-poky-linux-gnueabi

  • qemuarm-poky-linux-gnueabi

  • x86_64-linux

The directories found here and their contents are architecture and machine dependent. We shouldn't take this as a final list, only as an illustration. The directory x86_64-linux is used to build the host sysroot content, which is detailed in the next section. The directory all-poky-linux holds the working build directories for the packages that are architecture agnostic. This fragmented structure is necessary to allow building multiple machines and architectures within one build directory without conflicting with each other.

The target machine we use is qemuarm. This machine is an emulation of the ARM Versatile Platform Baseboard with the ARM926EJ-S CPU emulation that supports the ARMv5TE instructions. Poky treats qemuarm as a type...

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 €18.99/month. Cancel anytime