i'm trying debug in yocto build , bitbake -e accepted answer tracking variable assignments in bitbake of no help.
in particular situation, do_install step exhibiting different value of workdir preceding steps do_compile. particular recipe, install steps , subsequent packaging steps use different workdir, , bitbake-generated run.* , log.* files under directory.
when use -e option of bitbake, shows do_compile value of workdir, though step done/stamped , next outstanding step do_install. in other words, -e option failing evaluate rule base , perform assignments in exact manner matching step performed.
i tried combining -e -c option select build step; i.e. bitbake -e -c install <target>. ignores build step , dumps generic environment has workdir value used do_compile.
how actual variable assignment history build step happening or happen?
Comments
Post a Comment