[meta-freescale] [PATCH 2/2] weston-imx: Add dummy weston.ini

[Khem Raj]

On Wed, Nov 7, 2018 at 2:47 PM Andreas Müller <schnitzeltony at gmail.com>
wrote:

> On Wed, Nov 7, 2018 at 11:31 PM Khem Raj <raj.khem at gmail.com> wrote:
> >
> > On Wed, Nov 7, 2018 at 2:20 PM Andreas Müller <schnitzeltony at gmail.com>
> wrote:
> > >
> > > On Wed, Nov 7, 2018 at 10:59 PM Khem Raj <raj.khem at gmail.com> wrote:
> > > >
> > > > When building for non-imx platforms we get warnings e.g.
> > > >
> > > > meta-freescale/recipes-graphics/wayland/weston_4.0.0.imx.bb: Unable
> to
> > > > get checksum for weston SRC_URI entry weston.ini: file could not
> > > >  be found
> > > >
> > > I think the question is how do non imx platforms get affected by
> > > weston-imx - that should not happen - right?
> > >
> >
> > right. Here however we are dealing with a weston fork which is in
> > meta-fsl BSP layer and it only tested with subset of machines. But
> > in a multi-BSP distro like https://github.com/YoeDistro/yoe-distro
> > we enable many BSPs in single project and MACHINE can be
> > set to non imx based machine.
> >
> > So either this recipe gets limited to just those imx machines or
> > provides needed files so it can atleast parse
> >
> Ahh - parsing is the problem was not aware.
>
> At work I have a multi (4) BSP too and switch machines more or less
> daily. Since I don't have this issue (yet) I think it is maybe caused
> by [1] and the solution should be to follow split too - what do you
> think?
>

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

>
> [1]
> http://git.openembedded.org/openembedded-core/commit/?id=0f43ea8510ae6148a49eb25accac407b6b301b43
>
> Andreas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20181107/9449a790/attachment.html>