menuconfig task for kernels

[Przemyslaw Wesolek <przemyslaw.wesolek@cs.put.poznan.pl>]

Hi,

today I decided to modify the kernel compiled by OE. Accidentally, in
the same time a person on IRC pointed out problems with that. After some
investigation we discovered that menuconfig task in kernels is somewhat
misleading, if not broken.

The order of tasks to do menuconfig is, more or less: fetch, patch,
menuconfig. It means that when menuconfig is run, there is no .config*
files in linux build dir, and generated .config is far different than
defconfig resulting from applying OE patches.

The order for correct configuring of Linux is: fetch, patch, configure,
so I tried:

  1. bitbake virtual/kernel -c configure
  2. bitbake virtual/kernel -c menuconfig
  3. bitbake virtual/kernel

and this allowed me to apply my local changes to OE-proposed .config.

Is this the "right" way to do? If so, maybe menuconfig should be added
as 'after do_configure', instead of 'after do_patch'?

Przemek