[oe] build dependency cycles in openembedded

[Takeshi Hamasaki]

Hi,

you can find the line like:
DEPENDS = "XXXXXX-native"
in some recipes.

So, you can describe dependency to native tools from target build if necessary.
I guess this is the answer for the sentence what I have read the
second paragraph of [1]:

> Since the full distribution for the new architecture is not yet available,
> dependency cycles have to be broken during cross as well as native compilation.

I can't answer "how" the dependency to XXXX-native chosen, in which
recipe and to which native tools.
When I start to try OpenEmbedded, the dependencies were already well-built.
Maybe there is someone who can answer for deeper question.

Regards,
-- 
Takeshi Hamasaki

2013/2/18 Johannes Schauer <j.schauer at email.de>:
> Dear list,
>
> I am analyzing build dependency graphs for rpm and deb based binary
> distributions. I gave a talk about my work on this years FOSDEM [1]. To improve
> my work I was looking into Gentoo and Openembedded.
>
> While build dependency cycles in Gentoo are easily taken care of by manually
> compiling some source packages with different USE flags, how is this topic
> handled in OpenEmbedded?
>
> Searching the wiki, mailinglist and internet I was not able to find good
> sources which explain how serious the problem of build dependency cycles in
> OpenEmbedded is when bootstrapping a new target from nothing. I also did not
> find how build dependency cycles are dealt with, should they occur.
>
> Could you direct me to some resources which document the status and handling of
> build dependency cycles in OpenEmbedded?
>
> Thanks!
>
> cheers, josch
>
> [1] https://fosdem.org/2013/schedule/event/debian_bootstrap/
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel