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 placed inside the working directory of your project, usually tmp/work, and classified according to their architecture. For example, on a wandboard build, we find the following directories:

• all-poky-linux: This is used for architecture-independent packages
• cortexa9hf-neon-poky-linux-gnueabi: This is used for cortexa9, hard floating point packages
• cortexa9hf-neon-mx6qdl-poky-linux-gnueabi: This is used for cortexa9, hard floating point packages that are specific to the i.MX6 architecture
• wandboard-poky-linux-gnueabi: This is used for machine-specific packages, in this case wandboard
• x86_64-linux: This is used for the packages that form the host sysroot
• x86_64-nativesdk-pokysdk-linux: This is used...