[yocto] Easy tracking of dependencies

[Martin Jansa]

On Tue, Sep 22, 2015 at 03:11:03PM +0200, Gilles CARRY wrote:
> Hello,
> 
> I'm facing many cases in which bitbake spuriously rebuilds too many (all?) components despite the shared state cache. I'm not detailing these cases as I know it just a matter of variables and new tasks we added in our build process.
> My concern is about how I can track these dependencies when the spurious rebuilds occur. I have done this in the past and used commands or log files explaining what caused the rebuild of such or such component. Unfortunately, I just can't remember what it was. (my fault)
> 
> Does Yocto provide a way to track these dependencies? (ie. This task was triggered because this variable changed)
> Sorry if this question has already been asked but I'm failing to find the answer from the Yocto doc or from the web.

I'm using scripts/sstate-diff-machines.sh to create snapshots of all
relevant sstate signatures for all interesting builds (like our daily
official build) then it's easy to compare current signatures against
yesterday's official build when spurious rebuilds occur.

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20150922/0f903b18/attachment.pgp>