[oe] build dependency cycles in openembedded

[Khem Raj]

On (19/02/13 11:46), Johannes Schauer wrote:
> Hi,
> 
> Quoting Andreas Müller (2013-02-18 21:15:43)
> > FWIW long time ago in meta-oe commit 5b8522e3b592c96ec9325aff4bbaa68972e52d5b
> > gvfs-gdu-volume-monitor was spitted out into an own recipe to break
> > dependency loop for gvfs.
> 
> If I read this correctly, then this means that for some software packages,
> multiple bitbake recipes exist for the purpose of breaking dependency cycles?
> 
> How does the generation of build order work? Which algorithm handles the
> selection of recipes such that build dependency cycles are avoided? And once a
> recipe which was used to break a dependency cycle was compiled, how is the
> recompilation of the *full* package scheduled?

bitbake handles the built dependencies and runqueue generation which
decided the order or task execution. You should read about bitbkake
internals if you are interested in internal functioning of dep
resolution in bitbake.