Re: Cloning arch-independant KConfig

From: Joel Becker
Date: Thu Aug 12 2010 - 21:31:34 EST


On Fri, Aug 13, 2010 at 03:20:52AM +0200, Sam Ravnborg wrote:
> Today there are a few ways you can do so already.
> Say that you have saved away the known good one as "good", which is
> a direct copy of your .config.
>
> Then you can do for example:
> KCONFIG_ALLCONFIG=good make alldefconfig
>
> This will produce a config wich is almost equal to what you had before,
> and with defaults for all new stuff.
> I tested it where I used a sparc defconfig as input to a i386
> config and it just worked.

That seems pretty reasonable.

> cat .config good > new
> mv new .config
> make menuconfig
>
> This will trigger a lot of override warnings - which you just ignore.
> Resulting config is then mostly from "good".

The problem with this, which I've definitely done before, is I
never know what paths in menuconfig to look down. The alldefconfig
choice seems saner because it provides a dirt-simple CPU setup.

Joel

--

"Can any of you seriously say the Bill of Rights could get through
Congress today? It wouldn't even get out of committee."
- F. Lee Bailey

Joel Becker
Consulting Software Developer
Oracle
E-mail: joel.becker@xxxxxxxxxx
Phone: (650) 506-8127
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/