Reputation: 2744
In Yocto-based Embedded Linux distributions, I am really interested in finding the complete list of packages/recipes/kernel modules from each dependent layers that will be built and installed to an image file before executing the image building recipe such as:
bitbake my-image-minimal
Is there a way to achieve this? Any guidance in this regard is appreciated.
Thanks in advance.
Upvotes: 27
Views: 52098
Reputation: 857
You can find the list in the generated .manifest
file.
See IMAGE_MANIFEST
Upvotes: 8
Reputation: 421
We've talked about this in the past and for various reasons, it is hard to know what packages would end up in the image, without going through the complete build process.
One of the best tools for seeing what is an an image is the buildhistory
class. Add it to your user classes in local.conf
. The output ends up in the build directory within the buildhistory
sub-directory.
Upvotes: 0
Reputation: 330
Add INHERIT += "buildhistory"
in your conf/local.conf
and rebuild.
Upvotes: 0
Reputation: 1116
Yes,
Yocto maintains packages information in a form of manifest file located in
<"your_build_folder">/tmp/deploy/images/<"machine_image">/<"image_name">.manifest.
Upvotes: 26
Reputation: 3205
Yes, like this on old Bitbake versions:
bitbake -g <image> && cat pn-depends.dot | grep -v -e '-native' \
| grep -v digraph | grep -v -e '-image' | awk '{print $1}' | sort | uniq
Taken from the NXP Community website
On newer:
bitbake -g <image> && cat pn-buildlist | grep -ve "native" | sort | uniq
Upvotes: 33