Re: Arch specific/multiple Configure.help files?

Giacomo Catenazzi
2001-04-06T07:00:04Z

johan.adolfsson@axis.com wrote:
>
> I went ahead and implemented the change last night anyway and I
> will submit the patches and see if it will be accepted or not.
> The idea is that it first check in arch/$ARCH/Configure.help
> and if the file or the help is not found there,
> check Documentation/Configure.help.
>
> I believe there is an advantage from a maintenance point of view.
> It least for our CRIS architecture, I don't think it's any benefit to
> "bloat" the Documentation/Configure.help with a lot of
> CONFIG_ETRAX entries for the various hardware inerfaces
> when the help and config can be kept locally.
>

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.

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

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).

It is also designed so that a distribution can include
a translation of Configure.help. (But we don't expect
to include translation in std linux kernel)

> BTW: I added this to scripts/Configure and scripts/Menuconfig
> but I know to little tcl/tk to get it to work for the xconfig case.
> The variable $ARCH was not found and I don't know how to make
> it get it from the environment variables.
>

$ARCH is set on the top of the main Makefile. You can copy
the small shell script from here.

giacomo

> /Johan
>