Re: [PATCH] kconfig: use $K64BIT to set 64BIT with all*config targets

Adrian Bunk
2007-11-11T13:07:48Z

On Sun, Nov 11, 2007 at 01:43:28PM +0100, Guillaume Chazarain wrote:
> Hi Adrian,

Hi Guillaume,

> On 11/11/07, Adrian Bunk <bunk@kernel.org> wrote:
> > What exactly are the use cases where someone would need this?
>
> Glad you asked. Today, when I want to recompile a kernel while
> changing a CONFIG_ option, I manually edit the .config,
> remove the appropriate line and then run make oldconfig.
> I'd like to be able to do: make oldconfig CONFIG_FOO=bar.

first of all it's obvious that there can't be any guarantee that your
CONFIG_FOO variable will actually get the value bar since dependencies
might enable or disable it despite you wanting the opposite.

Another important point is that users that know about and see CONFIG_*
variables are kernel hackers, not the normal kconfig users.

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

And you won't upgrade the kernel you work against that
often compared to working on and testing of your own changes when
developing code.

> As you see, I'm more interested in make oldconfig than
> make all*config.

That's clear.

> Cheers.
> Guillaume

cu
Adrian

--

"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed