bitbake -c clean for all recipes

bitbake -c clean for all recipes

[Vajzovic, Tom]

Hi,

What command can I use to do the equivalent of running "bitbake -c clean" (or cleanstate etc) for all recipes that have previously been run?

Thanks,
Tom

Re: bitbake -c clean for all recipes

[Burton, Ross]

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

On 14 April 2016 at 12:18, Vajzovic, Tom <Tom.Vajzovic@irisys.co.uk> wrote:

> What command can I use to do the equivalent of running "bitbake -c clean"
> (or cleanstate etc) for all recipes that have previously been run?
>

The easy answer here is rm -rf tmp/.  What do you actually want to do?

Ross

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

Re: bitbake -c clean for all recipes

[Khem Raj]

On Thu, Apr 14, 2016 at 4:18 AM, Vajzovic, Tom
<Tom.Vajzovic@irisys.co.uk> wrote:
> Hi,
>
> What command can I use to do the equivalent of running "bitbake -c clean" (or cleanstate etc) for all recipes that have previously been run?

Thats almost equivalent of rm -rf tmp
since you have sstate it should rebuild really quick.

>
> Thanks,
> Tom
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: bitbake -c clean for all recipes

[Vajzovic, Tom]

Hi Ross & Raj,

From: Burton, Ross [mailto:ross.burton@intel.com] 
Sent: 14 April 2016 17:25
>
> On 14 April 2016 at 12:18, Vajzovic, Tom <Tom.Vajzovic@irisys.co.uk> wrote:
> What command can I use to do the equivalent of running 
> "bitbake -c clean" (or cleanstate etc) for all recipes that have previously been run?
> 
> The easy answer here is rm -rf tmp/.  

And what about cleanstate or cleanall?

> What do you actually want to do?

What I want to do is be certain that I am in the exact state that I would be in if I had made a clean checkout and then build from scratch.

The particular case that made me ask was that I added BB_GENERATE_MIRROR_TARBALLS = "1" to local.conf and wanted to trigger doing that.  The fact that just running bitbake <imagename> didn't do it made me paranoid about what other changes I might make that wouldn't get picked up, so I want to know how to roll back to set points in the build process and build from there (eg: clean, cleanstate, cleanall and any others that you can tell me about).

Many thanks,
Tom

Re: bitbake -c clean for all recipes

[Andre McCurdy]

On Fri, Apr 15, 2016 at 12:18 AM, Vajzovic, Tom
<Tom.Vajzovic@irisys.co.uk> wrote:
> Hi Ross & Raj,
>
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: 14 April 2016 17:25
>>
>> On 14 April 2016 at 12:18, Vajzovic, Tom <Tom.Vajzovic@irisys.co.uk> wrote:
>> What command can I use to do the equivalent of running
>> "bitbake -c clean" (or cleanstate etc) for all recipes that have previously been run?
>>
>> The easy answer here is rm -rf tmp/.
>
> And what about cleanstate or cleanall?

  clean : roughly the same as removing tmp
  cleansstate : roughly the same as removing tmp and sstate-cache
  cleanall : roughly the same as removing tmp, sstate-cache and downloads

>> What do you actually want to do?
>
> What I want to do is be certain that I am in the exact state that I would be in if I had made a clean checkout and then build from scratch.

Then remove tmp, sstate-cache and downloads. To be certain, remove
your build directory too.

There's not usually any need to do this kind of thing though (apart
from as a learning exercise).

> The particular case that made me ask was that I added BB_GENERATE_MIRROR_TARBALLS = "1" to local.conf and wanted to trigger doing that.  The fact that just running bitbake <imagename> didn't do it made me paranoid about what other changes I might make that wouldn't get picked up, so I want to know how to roll back to set points in the build process and build from there (eg: clean, cleanstate, cleanall and any others that you can tell me about).
>
> Many thanks,
> Tom
>
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto