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

Building an image using Hob

Our first step is to set up our build environment, as follows:

$: source poky/oe-init-build-env [build-directory]

We can choose an old build directory or create a new one.

Now, Hob is ready for use. To start it, we should run the following:

$: hob

At startup, Hob performs some parsing tasks, reading the local configuration and available metadata layers. After a short time, Hob proposes a list of available machines. We can select, for example, qemuarm.

Once the dependency tree is built, select the desired image, for example, core-image-full-cmdline.

The following screenshot shows the MACHINE variable content and the image to be built in the Hob interface:

Building an image using Hob

With the target MACHINE and image selected, the next step is to choose some advanced configuration, such as image types (for example, cpio.gz, ext2.bz2, ext3.gz, jffs2, ubifs, and vmdk) or package formats (rpm, deb, IPK, or TAR). We can also exclude all packages under the GPLv3 licensing, as shown in Chapter 13,...

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