* Does it possible to use pre-built native tools
@ 2009-12-08 7:55 Guo Hongruan
2009-12-08 8:07 ` Koen Kooi
0 siblings, 1 reply; 6+ messages in thread
From: Guo Hongruan @ 2009-12-08 7:55 UTC (permalink / raw)
To: openembeded-devel
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
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Does it possible to use pre-built native tools 2009-12-08 7:55 Does it possible to use pre-built native tools Guo Hongruan @ 2009-12-08 8:07 ` Koen Kooi 2009-12-08 8:56 ` Guo Hongruan 0 siblings, 1 reply; 6+ messages in thread From: Koen Kooi @ 2009-12-08 8:07 UTC (permalink / raw) To: openembedded-devel 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Does it possible to use pre-built native tools 2009-12-08 8:07 ` Koen Kooi @ 2009-12-08 8:56 ` Guo Hongruan 2009-12-08 9:06 ` Frans Meulenbroeks 0 siblings, 1 reply; 6+ messages in thread From: Guo Hongruan @ 2009-12-08 8:56 UTC (permalink / raw) To: openembedded-devel 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Does it possible to use pre-built native tools 2009-12-08 8:56 ` Guo Hongruan @ 2009-12-08 9:06 ` Frans Meulenbroeks 2009-12-08 9:42 ` Guo Hongruan 0 siblings, 1 reply; 6+ messages in thread From: Frans Meulenbroeks @ 2009-12-08 9:06 UTC (permalink / raw) To: openembedded-devel 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 > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Does it possible to use pre-built native tools 2009-12-08 9:06 ` Frans Meulenbroeks @ 2009-12-08 9:42 ` Guo Hongruan 2009-12-08 14:35 ` Chris Larson 0 siblings, 1 reply; 6+ messages in thread From: Guo Hongruan @ 2009-12-08 9:42 UTC (permalink / raw) To: openembedded-devel 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Does it possible to use pre-built native tools 2009-12-08 9:42 ` Guo Hongruan @ 2009-12-08 14:35 ` Chris Larson 0 siblings, 0 replies; 6+ messages in thread From: Chris Larson @ 2009-12-08 14:35 UTC (permalink / raw) To: openembedded-devel 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. ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2009-12-08 14:37 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2009-12-08 7:55 Does it possible to use pre-built native tools Guo Hongruan 2009-12-08 8:07 ` Koen Kooi 2009-12-08 8:56 ` Guo Hongruan 2009-12-08 9:06 ` Frans Meulenbroeks 2009-12-08 9:42 ` Guo Hongruan 2009-12-08 14:35 ` Chris Larson
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.