[bitbake-devel] [PATCH 0/2] Signature-based rebuild improvements

[Jason Wessel]

On 06/18/2012 10:45 AM, Paul Eggleton wrote:
> The following changes (against poky, but apply cleanly with -p2 against
> bitbake master) are available in the git repository at:
> 
>   git://git.yoctoproject.org/poky-contrib paule/bb-forcebuild
>   http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/bb-forcebuild
> 
> Paul Eggleton (2):
>   bitbake: ensure -f causes dependent tasks to be re-run
>   bitbake: add -C option to invalidate a task and rebuild the target
> 
>  bitbake/bin/bitbake        |    3 +++
>  bitbake/lib/bb/build.py    |   18 ++++++++++++++++++
>  bitbake/lib/bb/cooker.py   |    6 +++---
>  bitbake/lib/bb/runqueue.py |   28 ++++++++++++++++++++++------
>  bitbake/lib/bb/siggen.py   |   35 +++++++++++++++++++++++++++++++++++
>  5 files changed, 81 insertions(+), 9 deletions(-)
> 


While the use cases described in the defect work, there is a new side effect.  The sstate dir starts to fill up with new sums for the what ever package you compile.  Perhaps this is some kind of trade off we have to live with, but I do thing it is worth discussing.

I start with a fully populated sstate.  I didn't make any code changes at all to any package, I just wanted to see the compile log from acl in this case.

    bitbake -f -c compile acl
    bitbake acl

The sstate sum is completely different due to the hash injection, but the code compiled for everything is the same.  There is probably no easy, cheap (as in cpu/wall time) way to have the best of both worlds.

Jason.