Re: build dependency cycles in openembedded

[Takeshi Hamasaki <hmatrjp@users.sourceforge.jp>]

Before continuing to write reply,
I want to make sure about the usage of the word "native":

in OpenEmbedded recipe, let's say, when you work on a x86-64 system to build
for target system which has ARM architecture,

if you want to borrow a xz tool from x86-64 environment: you can write
 DEPENDS = xz-native

if you depends on xz tool build on target environment: you just write
 DEPENDS = xz

Is this the custom you assume?

What I had to find was the word "native" is used to point the target environment
in [1].
-- 
Takeshi Hamasaki

2013/2/18 Johannes Schauer <j.schauer@email.de>:
> Hi,
>
> Quoting Takeshi Hamasaki (2013-02-18 13:26:38)
>> 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.
>
> Sure, when cross compiling you can satisfy lots of dependencies by native
> binaries but others need the foreign version. In Debian based distribution,
> this distinction for cross build dependency resolution is made using
> Multi-Arch.
>
> Since some of the cross build dependencies can be satisfied by (already
> available) native tools, the dependency cycle situation is *much* less severe
> during cross compilation than it is during native compilation.
>
> But still, even when one wants to cross compile a native, minimal Debian build
> system (just containing the init, shell and compiler) one runs into build
> dependency cycles because some dependencies have to be satisfied by foreign
> (not yet built) binaries and thereby creating some dependency cycles.
>
> Is it different in OpenEmbedded?
>
> cheers, josch
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel