thoughts on coalescing libbb/ source files

[Rob Landley]

On Monday 27 March 2006 9:14 am, Robert P. J. Day wrote:
> i realize it's a heretical suggestion but is there a point where
> possibly saving a few hundred bytes becomes more trouble than it's
> worth?

If so, we haven't reached it yet.

What might be better is some way to scan a normal .c file, produce a list of 
all the function names in it, produce the .o list for that that the makefile 
can use, and iteratively build each one via some kind of preprocessing.  That 
way we could do something like:

$(decompose thing.c): thing.c
	decompose_build thing.c

And decompose would spit out the list of .om files that thing.c created, and 
decompose_build would iteratively produce those suckers by running some 
hideous sed invocation against the source to produce little temporary .c 
files containing just that one function and its #includes.

This is all speculation, of course, about a possible alternative to how 
xfuncs.c is built now, with less work spent on markup.  For now, xfuncs.c 
works fine.

> rday

Rob

> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/cgi-bin/mailman/listinfo/busybox

-- 
Never bet against the cheap plastic solution.