Does it possible to use pre-built native tools

Does it possible to use pre-built native tools

[Guo Hongruan]

Hi guys,
      I want to configure openembedded to use the pre-built native tools.
e.g: qemu-native, quilt-native when building the whole image, so that the
building can save lots of time. Is there anyone know how to achieve it?

      Thanks a lot!


-- 
Guo Hongruan, Embedded Linux Consultant
Mobile: +86-0-13484056007
Skype: camelguo
Twitter: camelguo
http://www.gulessoft.com

Re: Does it possible to use pre-built native tools

[Koen Kooi]

On 08-12-09 08:55, Guo Hongruan wrote:
> Hi guys,
> I want to configure openembedded to use the pre-built native tools.
> e.g: qemu-native, quilt-native when building the whole image, so that the
> building can save lots of time. Is there anyone know how to achieve it?

It won't save you any time, since every tool OE builds for it self is 
built for a reason. If you think a 10 minute buildtime improvement 
outweighs a month more of bughunting then look into ASSUME_PROVIDED.

regards,

Koen

Re: Does it possible to use pre-built native tools

[Guo Hongruan]

Hi Koen,
    Thanks for your information.
    I think it will save my time. Consider I have to build several  
platforms for different architecture, in fact the native tools is  
architecture independent. So I think it is more reasonable to avoid  
building native tools for other platforms. Is there anything wrong with me.


    I tried to use ASSUME_PROVIDED to avoid compiling some native tools,  
but it seems that there are some building failure. I am trying to figure  
them out.

在 Tue, 08 Dec 2009 16:07:25 +0800，Koen Kooi <k.kooi@student.utwente.nl>  
写道:

> On 08-12-09 08:55, Guo Hongruan wrote:
>> Hi guys,
>> I want to configure openembedded to use the pre-built native tools.
>> e.g: qemu-native, quilt-native when building the whole image, so that  
>> the
>> building can save lots of time. Is there anyone know how to achieve it?
>
> It won't save you any time, since every tool OE builds for it self is  
> built for a reason. If you think a 10 minute buildtime improvement  
> outweighs a month more of bughunting then look into ASSUME_PROVIDED.
>
> regards,
>
> Koen
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


-- 
Guo Hongruan, Embedded Linux Consultant
Mobile: +86-0-13484056007
Skype: camelguo
Twitter: camelguo
http://www.gulessoft.com

Re: Does it possible to use pre-built native tools

[Frans Meulenbroeks]

2009/12/8 Guo Hongruan <camelguo@gmail.com>:
> Hi Koen,
>   Thanks for your information.
>   I think it will save my time. Consider I have to build several platforms
> for different architecture, in fact the native tools is architecture
> independent. So I think it is more reasonable to avoid building native tools
> for other platforms. Is there anything wrong with me.

If you build different machines in the same tmp dir the system will
normally not rebuild native packages.
Also if it is the same architecture you won't get a new compiler (e.g.
if you have two armv5 systems).
Thinking of it, not sure what would happen if one version would insist
on using an older version of gcc

Frans
>
>
>   I tried to use ASSUME_PROVIDED to avoid compiling some native tools, but
> it seems that there are some building failure. I am trying to figure them
> out.
>
> 在 Tue, 08 Dec 2009 16:07:25 +0800，Koen Kooi <k.kooi@student.utwente.nl> 写道:
>
>> On 08-12-09 08:55, Guo Hongruan wrote:
>>>
>>> Hi guys,
>>> I want to configure openembedded to use the pre-built native tools.
>>> e.g: qemu-native, quilt-native when building the whole image, so that the
>>> building can save lots of time. Is there anyone know how to achieve it?
>>
>> It won't save you any time, since every tool OE builds for it self is
>> built for a reason. If you think a 10 minute buildtime improvement outweighs
>> a month more of bughunting then look into ASSUME_PROVIDED.
>>
>> regards,
>>
>> Koen
>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>
> --
> Guo Hongruan, Embedded Linux Consultant
> Mobile: +86-0-13484056007
> Skype: camelguo
> Twitter: camelguo
> http://www.gulessoft.com
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: Does it possible to use pre-built native tools

[Guo Hongruan]

Hi frans,
   In fact, I need to build completely different images for different  
architecture in different tmp directories. We need to do nightly build on  
build machine. So I think it would be better for several builds using the  
same one native tools set. It does not need to build native tools from  
zero on every time.



在 Tue, 08 Dec 2009 17:06:27 +0800，Frans Meulenbroeks  
<fransmeulenbroeks@gmail.com> 写道:

> 2009/12/8 Guo Hongruan <camelguo@gmail.com>:
>> Hi Koen,
>>   Thanks for your information.
>>   I think it will save my time. Consider I have to build several  
>> platforms
>> for different architecture, in fact the native tools is architecture
>> independent. So I think it is more reasonable to avoid building native  
>> tools
>> for other platforms. Is there anything wrong with me.
>
> If you build different machines in the same tmp dir the system will
> normally not rebuild native packages.
> Also if it is the same architecture you won't get a new compiler (e.g.
> if you have two armv5 systems).
> Thinking of it, not sure what would happen if one version would insist
> on using an older version of gcc
>
> Frans
>>
>>
>>   I tried to use ASSUME_PROVIDED to avoid compiling some native tools,  
>> but
>> it seems that there are some building failure. I am trying to figure  
>> them
>> out.
>>
>> 在 Tue, 08 Dec 2009 16:07:25 +0800，Koen Kooi  
>> <k.kooi@student.utwente.nl> 写道:
>>
>>> On 08-12-09 08:55, Guo Hongruan wrote:
>>>>
>>>> Hi guys,
>>>> I want to configure openembedded to use the pre-built native tools.
>>>> e.g: qemu-native, quilt-native when building the whole image, so that  
>>>> the
>>>> building can save lots of time. Is there anyone know how to achieve  
>>>> it?
>>>
>>> It won't save you any time, since every tool OE builds for it self is
>>> built for a reason. If you think a 10 minute buildtime improvement  
>>> outweighs
>>> a month more of bughunting then look into ASSUME_PROVIDED.
>>>
>>> regards,
>>>
>>> Koen
>>>
>>>
>>> _______________________________________________
>>> Openembedded-devel mailing list
>>> Openembedded-devel@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>>
>> --
>> Guo Hongruan, Embedded Linux Consultant
>> Mobile: +86-0-13484056007
>> Skype: camelguo
>> Twitter: camelguo
>> http://www.gulessoft.com
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


-- 
Guo Hongruan, Embedded Linux Consultant
Mobile: +86-0-13484056007
Skype: camelguo
Twitter: camelguo
http://www.gulessoft.com

Re: Does it possible to use pre-built native tools

[Chris Larson]

You'd likely be better off looking into the use of packaged staging packages
than using ASSUME_PROVIDED.

On Tue, Dec 8, 2009 at 2:42 AM, Guo Hongruan <camelguo@gmail.com> wrote:

> Hi frans,
>  In fact, I need to build completely different images for different
> architecture in different tmp directories. We need to do nightly build on
> build machine. So I think it would be better for several builds using the
> same one native tools set. It does not need to build native tools from zero
> on every time.
>
>
>
> 在 Tue, 08 Dec 2009 17:06:27 +0800，Frans Meulenbroeks <
> fransmeulenbroeks@gmail.com> 写道:
>
>
>  2009/12/8 Guo Hongruan <camelguo@gmail.com>:
>>
>>> Hi Koen,
>>>  Thanks for your information.
>>>  I think it will save my time. Consider I have to build several platforms
>>> for different architecture, in fact the native tools is architecture
>>> independent. So I think it is more reasonable to avoid building native
>>> tools
>>> for other platforms. Is there anything wrong with me.
>>>
>>
>> If you build different machines in the same tmp dir the system will
>> normally not rebuild native packages.
>> Also if it is the same architecture you won't get a new compiler (e.g.
>> if you have two armv5 systems).
>> Thinking of it, not sure what would happen if one version would insist
>> on using an older version of gcc
>>
>> Frans
>>
>>>
>>>
>>>  I tried to use ASSUME_PROVIDED to avoid compiling some native tools, but
>>> it seems that there are some building failure. I am trying to figure them
>>> out.
>>>
>>> 在 Tue, 08 Dec 2009 16:07:25 +0800，Koen Kooi <k.kooi@student.utwente.nl>
>>> 写道:
>>>
>>>  On 08-12-09 08:55, Guo Hongruan wrote:
>>>>
>>>>>
>>>>> Hi guys,
>>>>> I want to configure openembedded to use the pre-built native tools.
>>>>> e.g: qemu-native, quilt-native when building the whole image, so that
>>>>> the
>>>>> building can save lots of time. Is there anyone know how to achieve it?
>>>>>
>>>>
>>>> It won't save you any time, since every tool OE builds for it self is
>>>> built for a reason. If you think a 10 minute buildtime improvement
>>>> outweighs
>>>> a month more of bughunting then look into ASSUME_PROVIDED.
>>>>
>>>> regards,
>>>>
>>>> Koen
>>>>
>>>>
>>>> _______________________________________________
>>>> Openembedded-devel mailing list
>>>> Openembedded-devel@lists.openembedded.org
>>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>>>
>>>
>>>
>>> --
>>> Guo Hongruan, Embedded Linux Consultant
>>> Mobile: +86-0-13484056007
>>> Skype: camelguo
>>> Twitter: camelguo
>>> http://www.gulessoft.com
>>>
>>> _______________________________________________
>>> Openembedded-devel mailing list
>>> Openembedded-devel@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>>
>>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>
>
> --
> Guo Hongruan, Embedded Linux Consultant
> Mobile: +86-0-13484056007
> Skype: camelguo
> Twitter: camelguo
> http://www.gulessoft.com
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>



-- 
Chris Larson
clarson at kergoth dot com
clarson at mvista dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Software Engineer
MontaVista Software, Inc.