[poky] How to build a kernel using menuconfig

[Gary Thomas]

On 2011-09-27 21:45, Darren Hart wrote:
>
>
> On 09/26/2011 06:45 AM, Gary Thomas wrote:
>> I'm working with a recent Poky checkout:
>>     meta-yocto        = "master:7a0cbe6b0e5185aebabedc515b427994bc2a15dc"
>>
>> I used to be able to do this:
>>     % bitbake<some-image>
>> This step builds everything, including the kernel
>>     % bitbake virtual/kernel -c menuconfig
>> Adjust some settings
>>     % bitbake virtual/kernel -c compile -f
>>     % bitbake virtual/kernel
>> Rebuild my image with the new kernel included
>>     % bitbake<some-image>
>>
>> In the past, this would let me adjust some kernel settings, e.g. add a new
>> module, then rebuild it and later add this to an image.  Sadly, when I run
>> through these steps with the current master, the new kernel gets compiled
>> (because I used -f), but not packaged.
>>
>> The only thing I've done differently, save updating master, is my build
>> today includes
>>     INHERIT += "rm_work"
>>
>> Am I missing something?
>>
>> How can I build the kernel and make these in-tree adjustments like I used to?
>> I do this to figure out what kernel settings to set/save for my final packaging.
>
>
> Yeah, this is standard kernel devel workflow. I typically use the kernel
> recipe name directly, but otherwise my process is the same. What happens
> now when you run "bitbake virtual/kernel" after the compile -f ?
>

As indicated above, nothing.  If I remove rm_work from my configuration
and then rebuild the kernel, it works as expected.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------