Re: [bitbake-devel] Trouble capturing layer revision as variable in recipe

["Richard Purdie" <richard.purdie@linuxfoundation.org>]

On Wed, 2021-08-25 at 15:26 +0000, chris.laplante@agilent.com wrote:
> > > However there are two problems:
> > >    1. Making an empty commit to meta-our-layer doesn’t cause the
> > > recipe to be re-run. What’s weird is that when I use ‘bitbake u-boot
> > > –e’, I can see that the value of  OUR_LAYER_COMMIT is indeed changing.
> > > And with bitbake-dumpsig  I can see that OUR_LAYER_COMMIT is in the
> > task deps for do_deploy.
> > >    2. If I build ‘u-boot’, then make an empty commit to
> > > meta-our-layer, and then run “bitbake-whatchanged u-boot”, I get a
> > > “The metadata is not deterministic  and this needs to be fixed.” error.
> > > 
> > > Am I misunderstanding the purpose of vardepvalue? I thought it could
> > > be used to here to help bitbake ‘see’ through values that otherwise change
> > unexpectedly.
> > 
> > I suspect you need to have bitbake always reparse the recipe too. Maybe
> > BB_DONT_CACHE = "1" ?
> 
> Thanks for the suggestion. I guess this is because unless BitBake sees that
> the recipe file(s) changed (or they use SRCREV = AUTOREV), it won't reparse
> stuff in general?

Correct, it doesn't reparse at each invocation as in general that would upset
users! It doesn't know it needs to reparse in this case.

Cheers,

Richard