Re: [PATCH 00/11] bitbake-diffsigs fixes/improvements

[Patrick Ohly <patrick.ohly@intel.com>]

On Fri, 2017-04-07 at 20:32 +1200, Paul Eggleton wrote:
> On Friday, 7 April 2017 8:29:18 PM NZST Paul Eggleton wrote:
> > On Friday, 7 April 2017 7:56:19 PM NZST Patrick Ohly wrote:
> > > Am I using the tool incorrectly or are my expectations wrong?
> > > 
> > > My expectation was that "bitbake-diffsigs -t m4 do_build" would tell me
> > > that m4 was rebuilt because some tasks that it depends on changed, and
> > > then I would drill down to those tasks, eventually arriving at
> > > do_install.
> > 
> > Hmm, something has gone wrong here because this is the exact scenario it's
> > supposed to handle. In my similar tests it did work, so I'm not sure why it
> > didn't work in this case - I'll have to give it a try here.
> 
> I send and then I immediately realised what might be wrong - you said you're 
> using poky master which implies that you haven't also applied the patches for 
> lib/oe/sstatesig.py that I sent to the OE-Core list today. If you haven't, try 
> doing that, it should fix the problem.

Indeed, I had missed that part. It's working now for do_install.

What about do_build? Should bitbake-diffsigs be usable with that?

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.