fixing bbox build system

[Rob Landley]

On Thursday 05 October 2006 4:30 pm, Denis Vlasenko wrote:
> On Thursday 05 October 2006 16:15, Rob Landley wrote:
> > On Wednesday 04 October 2006 8:11 am, Bernhard Fischer wrote:
> > > >Also some more peculiar build modes (CONFIG_BUILD_LIBBUSYBOX,
> > > >CONFIG_BUILD_AT_ONCE) may be broken.
> > > 
> > > Let's drop CONFIG_BUILD_LIBBUSYBOX for now. CONFIG_BUILD_AT_ONCE is
> > > something i want to keep since it creates a smaller binary. Doesn't the
> > > kernel support this too, perhaps under a different name?
> > 
> > The kernel guys have poked at adding it (David Woodhouse, I think) but the 
> > patches haven't been merged yet that I'm aware of.  Also, they way they 
build 
> > is to do a directory at a time.  (You know how we're building various .a 
> > files and then linking them together?  Their build-at-once does each .a 
file 
> > in one gulp, not the whole project.)
> 
> Sure, kernelwide
> 
> find -name *.c | xargs gcc
> 
> would devour RAM like crazy 8)

Building busybox at once takes 400 megs and has no progress indicator at all 
until it finishes.

The other thing is that building each subdirectory at once seems to give them 
most of the benefits.  They don't consider building the whole project at once 
a good trade-off.

Rob
-- 
Never bet against the cheap plastic solution.