> > This was already discussed on kbuild list.
> > It is better to have only 1 Configure.help. This help
> > translation of the file and help busy developers.
> > They should not rewrite texts in every Configure.help.
> I can't see that 1 file makes it easier.
> The same help text is only present in one file,
> either arch/$ARCH/Configure.help or
Ok, if you use both files.
Better a single file because:
- I18n support. (But not a big issue for us).
- CML2 merges all arch configurations in one file (really in 4
rules, menu strings, ...)
Thus because we merge also configuration, I think that it is
not to split the helps.
- IIRC there is only few ARCH specific configuration, thus we
reduce the size of che Configure.help
Note that the arch/config.in have to much configuration item
(but they repeat in (nearly) all arch/config.in files, thus
should count only the really arch specific item.
I would prefer to have config.in and help file togheter. But
discussion in kbuild list, it come that is is better to merge
all configuration in one file and the strings in an other (and
not to merge Configure.help to not heve a very huge file).
What are the advanteget to split the Configure.help?
> The help system first checks the file in arch/$ARCH and if
> the help is not present there it checks the one in Documentation/
> > If you should provide a special help on a specific ARCH you
> > could modify the symbols: instead of
> > : bool 'std IPC support' CONFIG_IPC
> > you can do:
> > : bool 'arch specific IPC help' CONFIG_IPC_STRANGE_ARCH
> > : define_bool CONFIG_IPC CONFIG_IPC_STRANGE_ARCH
> Don't know if you missunderstood me or if I missunderstand
> you here.
> The typical use for the arch specific help file would only cover
> the arch specific CONFIG options (although it could "override"
> the general help text in Documentation/Configure.help with
> an arch specific one, but if you do that I guess you're doing
> something wrong)
I think I missunderstood you. But this was the big issue for
splitting Configure.help. (Thus if an developer should use
at arch specific help, he should use this method)
> > ESR CML2 have the defualt path for Configure.help build in
> > the rules files, but it can be overriden by command options
> > to use an other Configure.help (the format do not change).
> I want to be able to use two help files.
I think it is not a big issue. In Makefile we can
: cat Conf.help.1 Conf.help2 > .Conf.help
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Apr 07 2001 - 21:00:18 EST