On 11/11/07, Adrian Bunk <[EMAIL PROTECTED]> wrote: > Another important point is that users that know about and see CONFIG_* > variables are kernel hackers, not the normal kconfig users.
But kconfig is mainly for kernel hackers, otherwise it would be called CML2 ;-) > > Also, when working on a specific feature of the kernel, I tend to > > install both a kernel with the CONFIG_ option set and one with > > the option unset. Scripts to do that can twiddle the .config file, > > but it would be more convenient if kbuild could avoid that. > > I'm wondering why you don't use two different O= output directories > instead? > > Depending on the CONFIG_ option in question this might even greatly > reduce your compile times. /me is filled with wonder at the discovery that .config is saved in the O= directory. Thanks a lot Adrian for this time saver. So it's not strictly an output directory, more a build directory. I still think "make oldconfig CONFIG_FOO=bar" is useful for the occasional config change, but thanks again for this great tip. -- Guillaume - 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/