On Wed, 2017-03-01 at 04:00 +0000, Richard Purdie wrote: > On Tue, 2017-02-28 at 21:09 +0100, Patrick Ohly wrote: > > On Mon, 2017-02-20 at 15:12 -0600, Aníbal Limón wrote: > > > > > > common.test_signatures: Test executed in BSP and DISTRO layers to > > > review > > > doesn't comes with recipes that changes the signatures. > > I have a question about the goal for this test: is it meant to detect > > layers which incorrectly change the signatures of allarch recipes or > > recipes which share the same tune flags with other machines? > > > > Let's take MACHINE=edison as an example. > > The test is not for these things. Its using the sstate signatures for > something different compared to those other tests. > > The idea is that if you have a set of layers and generate the > signatures for world, then you add say a BSP layer but do not select > that MACHINE, the signatures should remain unchanged.
That's useful too, of course. Is the "build single distro for different machines" scenario that I described part of the Yocto Compliance 2.0? Should there be tests for it? -- 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. -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
