Exploring an image's contents

We have already seen how to use the build history feature to obtain a list of packages and files included in our image. In this recipe, we will explain how the root filesystem is built so that we are able to track its components.

Getting ready

When packages are built, they are classified inside the working directory of your project (tmp/work) according to their architecture. For example, on a wandboard-quad build, we find the following directories:

  • all-poky-linux: This is used for architecture-independent packages
  • cortexa9hf-vfp-neon-poky-linux-gnueabi: This is used for cortexa9, hard floating point packages
  • wandboard_quad-poky-linux-gnueabi: This is used for machine-specific packages; in this case, wandboard-quad
  • x86_64-linux ...

Get Embedded Linux for Developers now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.

Start your free trial