[BusyBox] What happened to --long-options?

Glenn McGrath bug1 at iinet.net.au
Wed Jan 19 08:40:34 UTC 2005


On Wed, 19 Jan 2005 00:55:14 -0500
Rob Landley <rob at landley.net> wrote:

> Okay, I remember there being a menuconfig option to enable/disable 
> --long-option support, but I can't find it in menuconfig of a current
> cvs  snapshot.  I mention this because I tried to use "mount --move"
> in a busybox  build yesterday, and it didn't recognize it.  A quick
> glance at the source  code shows the table of long options being
> defined, but I can't see where  it's ever being used...
> 
> Quite possibly I never understood how the long option parsing worked
> in the  first place.  (After "get complementally", I've pretty much
> stayed away from  that part of the code...)
> 
> But I'd rather like to make this work, and the default assumption is
> that I'm  doing something wrong.
> 
> Any clues?  This works for everybody else, I take it?

I dont think there was ever any global option to enable/disable long
options, there are a half-dozen applets that have a menu item to
enable/disable long options for that specific applet.

There may have been talk about a global option, im not aware of it being
implemented.

The bb_applet_long_options variable is used by an applet to make
bb_getopt_ulflags aware that the applet wants to use long options.

Actually, long options are one of the reasons bb_getopt_ulflags came
about, it has much lower overheads than glibc's getopt_long.



Glenn 



More information about the busybox mailing list