Closed cperrysfl closed 8 months ago
See also #216
I can assure the output is an excerpt from bitbake -e which indeed ends up being the same as bitbake-getvar. I usually introduce bitbake-getvar at that time or a bit earlier
Hello!
I've run the command again and looked a bit more carefully: The output of bitbake-getvar -r ninvaders DEPENDS
is indeed a subset of bitbake -e ninvaders
. The -e option seem to print every variables (with assignation history) for a given target, as well as all the tasks and shell/python functions.
I never realized the assignation history was in bitbake -e
as I'm always grepping the very large output it gives.
I have added bitbake-getvars in a different way. Thanks for your proposal @cperrysfl !
Hello,
There seems to be a problem with the "Debugging recipes" slide of the yocto-recipe-advanced.tex series of slides. The output of the command looks to be from
bitbake-getvar -r ninvaders DEPENDS
but the command entered isbitbake -e ninvaders
which prints a different output.I also found that there is no formal introduction to bitbake-getvar so I added one and moved this snippet of code sooner in the training.
Let me know if this seems OK to you.
Thank you, Charles