Bug 2256 - kernel menuconfig confusion with sstate

Bug 2256 - kernel menuconfig confusion with sstate

[Jürgen Messerer]

[-- Attachment #1: Type: text/plain, Size: 444 bytes --]

Dear Darren

You suggested in Bug 2256 the following:

$ bitbake virtual/kernel -c cleansstate
$ bitbake virtual/kernel -c menuconfig
$ bitbake virtual/kernel -c compile -f; bitbake virtual/kernel


Can you tell me what the difference is between
"bitbake virtual/kernel -c compile -f"
and
"bitbake virtual/kernel"

Shouldn't be the last command "bitbake -c deploy virtual/kernel"?

Thanks for the infos

Regards

Juergen


[-- Attachment #2: Type: text/html, Size: 4598 bytes --]

Re: Bug 2256 - kernel menuconfig confusion with sstate

[Darren Hart]

Hi Juergen,

On 06/15/2012 02:07 AM, Jürgen Messerer wrote:
> Dear Darren
> 
> You suggested in Bug 2256 the following:
> 
> $ bitbake virtual/kernel -c cleansstate
> 
> $ bitbake virtual/kernel -c menuconfig
> 
> $ bitbake virtual/kernel -c compile -f; bitbake virtual/kernel
> 
> Can you tell me what the difference is between
> 
> “bitbake virtual/kernel -c compile –f”
> 
> and
> 
> “bitbake virtual/kernel”

The -c argument specifies a specific task you want bitbake to execute,
it accepts values from the listtasks command, compile is one of them.
The -f argument forces the task to execute even if bitbake thinks it has
already performed the task. This is useful when changing the sources
manually, which bitbake can't know anything about.

Note that "bitbake -h" would have provided this information.

> 
> Shouldn’t be the last command “bitbake –c deploy virtual/kernel”?

If all you want is to get the bzImage into the tmp/deploy/images
directory, then that will suffice. If you want it to package it up and
complete all the tasks associated with the virtual/kernel recipe, then
"bitbake virtual/kernel" is required.

> 
> Thanks for the infos

Welcome.

> 
> Regards
> 
> Juergen

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel