[BusyBox] Changing the way help is displayed...
Vladimir N. Oleynik
dzo at simtreas.ru
Mon Apr 16 17:15:51 UTC 2001
Larry,
> There may not be a reason to have <appletname.h>. The only valid
> definition it would include is int <appletname>_main(). That can
> be generated without using a separate file.
1) For trivial generator busybox_applets.h
2) For aliases ("test"=="[", "init"=="linuxrc", "dos2unix"...)
...
N) For generate several binaries kit
> I guess <appletname>.cfg would be a default set, that could
> be overruled by the version in the current directory. This
> is a c-syntax file, that is #included by <appletname>.c?
Hmm, and create special C-compiler for parse this? ;-0 :-)
> The existing Config.h does the following:
> 1. applet selection
> 2. general system config
> 3. config for groups of related applets
> 4. individual applet config
> 5. interlocking against bogus configs
> Of these, (1) would move elsewhere, (4) is taken up with <appletname>.cfg.
> I'm not worried about (5), it's easy enough to split out. (2) is a
> legitimate part of a busybox-wide Config.h, but there isn't really
> that much -- BUFFERS_GO_ON_STACK and USE_DEVPS_PATCH.
> I don't know how to handle (4), except to leave it in Config.h until
> someone thinks of a convenient and productive way to pull it out.
May be use part current Config.h?
/* Hand manual section */
/* Comment for option XXX */
#define BB_OPTION_XXX
...
/* Automatic section, not change */
#include "../Common.Config.h"
#ifdef BB_OPTION_ABC
# undef BB_OPTION_XY
# define BB_OPTION_Z
#endif
#if defined(BB_OPTION_Z) && !defined(BB_OPTION_NNN)
#error Require option BB_OPTION_NNN in common Config.h for use BB_OPTION_Z
#endif
--w
vodz
More information about the busybox
mailing list