[oe] dependencies between packages

[C Michael Sundius]

>

> . In
> > fact even if recipe B is cleaned up:
> >
> >    bitbake -c clean B
> >
> > and then we run recipe A
> >
> >    bitbake A
> >
> > only recipe B is run and recipe A is NOT rerun! the dependency is
> satisfied
> > by rerunning recipe B and then bitbake stops..
> >
> > is this expected behaviour? Is there away to force rerunning of recipes
> that
> > would be "out of date" due to one of its dependent recipes being return
> and
> > re-staging (potentially) new headers and libraries?
> >
> > Any help of suggestions would be greatly appreciated.
> >
> > Mike
>
> If you change a recipe you should bump PR. in the recipe of B. That
> will cause that bitbake A will resuilt in a rebuild.
>
> Hmmm. nope... I bumped PR of B, then rebuilt A

vi B.bb    # change PR from r1 to r2
bitbake A

only caused B to be rebuilt. even though B may have staged completely
different headers or libraries.