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 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

Package feeds


As we discussed in Chapter 4, Grasping the BitBake Tool, packages play a central role, as images and SDKs rely on them. In fact, do_rootfs makes use of a local package repository to fetch the binary packages when generating the root filesystem. This repository is generally known as a package feed.

There is no reason for this repository to be used just for the images or SDK build steps. In fact, there are several valid reasons for making this repository remotely accessible internally in our development environment or publicly for use in the field. Some of these reasons are listed, including the following:

  • Easily testing an updated application during development stage, without the need of a complete system re-installation
  • Make additional packages more flexible so that they can be installed in a running image
  • Update products in the field

To produce a solid package feed, we must ensure that we have consistent increments in the package revision every time the package is changed. It is...

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