[busybox] v0.5 of busybox single-applet iterative build script

[Rob Landley]

On Wednesday 21 June 2006 3:16 pm, Bernhard Fischer wrote:
> On Wed, Jun 21, 2006 at 02:55:12PM -0400, Rob Landley wrote:
> >On Wednesday 21 June 2006 6:52 am, Bernhard Fischer wrote:
> >> >If you've got one I can just run in an empty directory that will do an
> >> >anonymous checkout of current and try a bunch of different ways of
> >> > building it, which I can just leave running for a while to find new
> >> > warnings and build breaks, that would be really cool.
> >>
> >> I've updated the abovementioned script accordingly.
> >> E.g.
> >> mkdir -p /tmp/scratch
> >> cd /tmp/scratch
> >> ~/bin/mk.busybox.sh
> >
> >It's grinding away in the background on my laptop right now...
>
> Spare your cycles. There were no errors about 6 hours ago (with
> my compiler)..
>
> It still is handy at times (e.g. in an alleged freeze-phase before a new
> release), IMO.

I'm actually tempted to go through and rename the applet configs CONFIG_APP 
(I.E. CONFIG_CP -> CONFIG_APP_CP).

Right now we've got CONFIG_FEATURE and CONFIG_DEBUG that our various 
config-twiddling tools can sink their teeth into, but no easy way to go "this 
is an applet".

The alternative is to find everything that _isn't_ an applet and give it an 
understandable prefix.  Your script has an interesting ignore list that's a 
good start fo rthis.

These don't start with "CONFIG_", and I'm thinking of moving most of them out 
of .config anyway:
  HAVE_DOT_CONFIG
  PREFIX
  CROSS_COMPILER_PREFIX
  EXTRA_CFLAGS_OPTIONS


Your list also has CONFIG_DEBUG and CONFIG_FEATURE_INSTALLER which we can 
already filter out...


That leaves:
  CONFIG_SHOW_USAGE
  CONFIG_SELINUX
  CONFIG_STATIC
  CONFIG_BUILD.*
  CONFIG_INSTALL_.*
  CONFIG_LFS
  CONFIG_NO_DEBUG_LIB
  CONFIG_DMALLOC
  CONFIG_EFENCE
  CONFIG_STRIP_BINARIES
  CONFIG_LOCALE_SUPPORT
  CONFIG_MD5_SIZE_VS_SPEED
  CONFIG_BUSYBOX_EXEC_PATH
  CONFIG_DEVFS
  CONFIG_VERBOSE_USAGE

Which should possibly have FEATURE stuck in their names...?

Hmmm...  If we're going to break people's .config files, now might be a good 
time.  On the other hand, I hope to come up with a release candidate this 
weekend and come out with the final 1.2.0 on the 30th...

Rob
-- 
Never bet against the cheap plastic solution.