You're reading from Embedded Linux Development Using Yocto Project Leverage the power of the Yocto Project to build efficient Linux-based products

Product type Paperback

Published in Apr 2023

Publisher Packt

ISBN-13 9781804615065

Length 196 pages

Edition 3rd Edition

Tools

Linux

Concepts

Operating Systems

Authors (2):

Otavio Salvador

Daiane Angolini

View More author details

Table of Contents (20) Chapters

Preface

1. Chapter 1: Meeting the Yocto Project

2. Chapter 2: Baking Our First Poky-Based System FREE CHAPTER

3. Chapter 3: Using Toaster to Bake an Image

4. Chapter 4: Meeting the BitBake Tool

5. Chapter 5: Grasping the BitBake Tool

6. Chapter 6: Detailing the Temporary Build Directory

7. Chapter 7: Assimilating Packaging Support

8. Chapter 8: Diving into BitBake Metadata

9. Chapter 9: Developing with the Yocto Project

10. Chapter 10: Debugging with the Yocto Project

11. Chapter 11: Exploring External Layers

12. Chapter 12: Creating Custom Layers

13. Chapter 13: Customizing Existing Recipes

14. Chapter 14: Achieving GPL Compliance

15. Chapter 15: Booting Our Custom Embedded Linux

16. Chapter 16: Speeding Up Product Development through Emulation – QEMU

17. Chapter 17: Best Practices

18. Index

Why subscribe?

19. Other Books You May Enjoy

Using the Standard SDK

Usually, an SDK has a set of libraries and applications it must provide, which is defined in an image tailored to the product. These are called image-based SDKs. For example, we can generate the Standard SDK for core-image-full-cmdline with the following command:

Figure 9.2 – How to generate the Standard SDK for core-image-full-cmdline

Another option is to create a generic SDK with the toolchain and debugging tools. This generic SDK is called meta-toolchain and is used mainly for Linux kernel and bootloader development and their debugging processes. It may not be sufficient to build applications with complex dependencies. To create meta-toolchain, use the following command:

Figure 9.3 – How to generate a generic SDK

In both cases, the resulting SDK self-installer files are at build/tmp/deploy/sdk/. Considering we used the Standard SDK for core-image-full-cmdline, we can see the following...