Yocto debugging commands
Notes about some useful Yocto debugging commands
Checking owner of installed files
Assuming that build environments is ready(which means you can run bitbake
normally), using oe-pkgdata-util
can help to find the recipe who populated it. i.e:
1 | oe-pkgdata-util find-path /lib/ld-2.28.so |
/lib/ld-2.28.so was installed by glibc
Checking packages are going to install
1 | bitbake -g <image> && cat pn-buildlist | grep -ve "native" | sort | uniq |
Checking packages installed
There are several .manifest files under the path of built images, which contained packages has been installed.
Checking variables inside recipes
bb.utils.contains
can help to check variables inside recipes. i.e. we’d like to install some files base on MACHINE_FEATURES :
1 | do_install() { |
Below is the python code from openembedded, which explains usage of this function:
1 | def contains(variable, checkvalues, truevalue, falsevalue, d): |