<div><br></div><div><br><div class="gmail_quote"><div dir="ltr">On Wed, Nov 7, 2018 at 2:47 PM Andreas Müller <<a href="mailto:schnitzeltony@gmail.com">schnitzeltony@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Nov 7, 2018 at 11:31 PM Khem Raj <<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>> wrote:<br>
><br>
> On Wed, Nov 7, 2018 at 2:20 PM Andreas Müller <<a href="mailto:schnitzeltony@gmail.com" target="_blank">schnitzeltony@gmail.com</a>> wrote:<br>
> ><br>
> > On Wed, Nov 7, 2018 at 10:59 PM Khem Raj <<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>> wrote:<br>
> > ><br>
> > > When building for non-imx platforms we get warnings e.g.<br>
> > ><br>
> > > meta-freescale/recipes-graphics/wayland/<a href="http://weston_4.0.0.imx.bb" rel="noreferrer" target="_blank">weston_4.0.0.imx.bb</a>: Unable to<br>
> > > get checksum for weston SRC_URI entry weston.ini: file could not<br>
> > >Â be found<br>
> > ><br>
> > I think the question is how do non imx platforms get affected by<br>
> > weston-imx - that should not happen - right?<br>
> ><br>
><br>
> right. Here however we are dealing with a weston fork which is in<br>
> meta-fsl BSP layer and it only tested with subset of machines. But<br>
> in a multi-BSP distro like <a href="https://github.com/YoeDistro/yoe-distro" rel="noreferrer" target="_blank">https://github.com/YoeDistro/yoe-distro</a><br>
> we enable many BSPs in single project and MACHINE can be<br>
> set to non imx based machine.<br>
><br>
> So either this recipe gets limited to just those imx machines or<br>
> provides needed files so it can atleast parse<br>
><br>
Ahh - parsing is the problem was not aware.<br>
<br>
At work I have a multi (4) BSP too and switch machines more or less<br>
daily. Since I don't have this issue (yet) I think it is maybe caused<br>
by [1] and the solution should be to follow split too - what do you<br>
think?<br>
</blockquote><div dir="auto"><br></div><div dir="auto">I think you must be seeing it too when building for non imx machine too but since it’s a warning you might be not seeing it breaking the builds but just delete the tmp and then set machine to say rpi3 and do a bitbake core-image-Weston </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
[1] <a href="http://git.openembedded.org/openembedded-core/commit/?id=0f43ea8510ae6148a49eb25accac407b6b301b43" rel="noreferrer" target="_blank">http://git.openembedded.org/openembedded-core/commit/?id=0f43ea8510ae6148a49eb25accac407b6b301b43</a><br>
<br>
Andreas<br>
</blockquote></div></div>