[PATCH 1/2] linux-imx-headers: Reduce visibility to imx host alone

[PATCH 1/2] linux-imx-headers: Reduce visibility to imx host alone

[Khem Raj]

It uses variables that are specific to meta-fsl layer and when using in
multi-BSP env this fails to expand those variables

Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
 recipes-kernel/linux/linux-imx-headers_4.9.123.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/recipes-kernel/linux/linux-imx-headers_4.9.123.bb b/recipes-kernel/linux/linux-imx-headers_4.9.123.bb
index 7be9cf94..77b05cff 100644
--- a/recipes-kernel/linux/linux-imx-headers_4.9.123.bb
+++ b/recipes-kernel/linux/linux-imx-headers_4.9.123.bb
@@ -55,3 +55,5 @@ do_install() {
 ALLOW_EMPTY_${PN} = "1"
 
 PACKAGE_ARCH = "${MACHINE_SOCARCH}"
+COMPATIBLE_HOST_imx = ".*"
+COMPATIBLE_HOST ?= "(none)"
-- 
2.19.1

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

[Khem Raj]

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

Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
 recipes-graphics/wayland/weston/weston.ini | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 recipes-graphics/wayland/weston/weston.ini

diff --git a/recipes-graphics/wayland/weston/weston.ini b/recipes-graphics/wayland/weston/weston.ini
new file mode 100644
index 00000000..a690506e
--- /dev/null
+++ b/recipes-graphics/wayland/weston/weston.ini
@@ -0,0 +1 @@
+# Please define a weston.ini if needed
-- 
2.19.1

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

[Andreas Müller]

On Wed, Nov 7, 2018 at 10:59 PM Khem Raj <raj.khem@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?

Andreas

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

[Khem Raj]

On Wed, Nov 7, 2018 at 2:20 PM Andreas Müller <schnitzeltony@gmail.com> wrote:
>
> On Wed, Nov 7, 2018 at 10:59 PM Khem Raj <raj.khem@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


> Andreas

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

[Andreas Müller]

On Wed, Nov 7, 2018 at 11:31 PM Khem Raj <raj.khem@gmail.com> wrote:
>
> On Wed, Nov 7, 2018 at 2:20 PM Andreas Müller <schnitzeltony@gmail.com> wrote:
> >
> > On Wed, Nov 7, 2018 at 10:59 PM Khem Raj <raj.khem@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?

[1] http://git.openembedded.org/openembedded-core/commit/?id=0f43ea8510ae6148a49eb25accac407b6b301b43

Andreas

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

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 1832 bytes --]

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

> On Wed, Nov 7, 2018 at 11:31 PM Khem Raj <raj.khem@gmail.com> wrote:
> >
> > On Wed, Nov 7, 2018 at 2:20 PM Andreas Müller <schnitzeltony@gmail.com>
> wrote:
> > >
> > > On Wed, Nov 7, 2018 at 10:59 PM Khem Raj <raj.khem@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
>

[-- Attachment #2: Type: text/html, Size: 2926 bytes --]