On Wed, 12 Apr 2006 13:00:22 +0200 (CEST) Roman Zippel wrote:
> Hi,
>
> On Sun, 9 Apr 2006, Randy.Dunlap wrote:
>
> > +void usage(char *progname)
> > +{
> > + printf("%s [-o|-s|-d|-D|-n|-m|-y|-r] Kconfig_filename\n", progname);
>
> |-D <config>|
>
> > + printf(" -o: oldconfig: ask only about new config symbols\n");
> > + printf(" -s: silentoldconfig: don't ask about any symbol values\n");
>
> It does ask about them, but suppresses a lot of prints.
>
> > + printf(" -d: defconfig: use default symbol values\n");
>
> To be precise it uses arch/$ARCH/defconfig as default values.
>
> > + printf(" -n: set unknown symbol values to 'n'\n");
> > + printf(" -m: set unknown symbol values to 'm'\n");
> > + printf(" -y: set unknown symbol values to 'y'\n");
>
> It actually tries to set all values to n/m/y.
>
> > @@ -546,8 +564,8 @@ int main(int ac, char **av)
> > break;
> > case 'h':
> > case '?':
> > - printf("%s [-o|-s] config\n", av[0]);
> > - exit(0);
> > + usage(av[0]);
> > + break;
>
> That's indeed a little obsolete. :-)
IMO the main points/questions are:
- where to document the command-line options and environment variables
(including the recent KCONFIG_CONFIG): in a usage() function or in
Documentation/kbuild/usage.txt file?
- if the answer above is in a usage() function, how does a user invoke
that help request? Doing "make config -h" doesn't work: 'make' sees
the -h and spits out its own help text. Would a special case of
'make config help' be acceptable or is this a good reason to use
a usage.txt file instead?
- or have you already taken care of all of this? 8;)
Thanks.
---
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]