Re: question about devtools-native tasks

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

On Mon, 2012-06-18 at 20:48 +0900, Bongseo Jang wrote:
> Hi All,
>  
> I'm watching console output of 'bitbake minimal-core-image'
> It starts with getting native devtools like,
>  
> NOTE: Running task 1 of 63 (ID:
> 11, /home/bsjang/poky/meta/recipes-devtools/quilt/quilt-native_0.60.bb, do_fetch)
> NOTE: Running task 2 of 63 (ID: 53,
> virtual:native:/home/bsjang/poky/meta/recipes-devtools/gnu-config/gnu-config_20111111.bb, do_fetch)
> NOTE: Running task 3 of 63 (ID:
> 60, /home/bsjang/poky/meta/recipes-devtools/m4/m4-native_1.4.16.bb,
> do_fetch)
> NOTE: Running task 4 of 63 (ID: 32,
> virtual:native:/home/bsjang/poky/meta/recipes-devtools/autoconf/autoconf_2.68.bb, do_fetch)
> 
> and then reads bblayers.conf, local.conf and so on which are
> actually asked to be done by me, right?
>  
> I'm wondering 
>      1) where the dependency on native devtools things are from
> (source level explanation or overall yocto/poky concept are all
> welcom) and 
>      2) can I use native tools which are already installed in my host
> linux distribution.(i don't want to fetch and compile the same tools
> again)

In general if its building it, its doing do for a reason. For autoconf
this is because of our own patches we need, for things like python/perl,
its because we need the exact same native version to be able to cross
compile effectively.

There are a small number of things like git-native which its probably
safe to ASSUME_PROVIDED but those are the exception rather than the
rule. We do this to ensure the same thing gets build regardless of which
system its built upon for build reproducibility.

Cheers,

Richard