The new meta-zephyr is work based on previous original work by
Randy Witt and Richard Purdie, so it is actually a second kick at the can.
One of the things I did when I originally put this together that could now
change is qemuzephyrrunner.py which is used in the tests. I did it because
runqe
implementation.
> -Original Message-
> From: Josef Holzmayr [mailto:holzm...@rsi-elektrotechnik.de]
> Sent: Tuesday, December 13, 2016 5:51 AM
> To: yocto@yoctoproject.org; Bystricky, Juro
> Subject: Re: [yocto] meta-zephyr layer
>
> Hello Juro,
>
> first off, thanks fo
Thanks, good point. The need for is poky.conf historic, not really needed at
all anymore.
From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Monday, December 12, 2016 4:00 PM
To: Bystricky, Juro
Cc: Philip Balister ; yocto@yoctoproject.org
Subject: Re: [yocto] meta-zephyr layer
On 12
Hello Juro,
first off, thanks for taking the kick, whatever its count is.
On 12.12.2016 23:15, Bystricky, Juro wrote:
Building of Zephyr images in Yocto can now be done fairly unobtrusively
via a new layer "meta-zephyr" and specifying a new distro in local.conf:
DISTRO="zephyr"
Leaving out th
On 12 December 2016 at 22:52, Bystricky, Juro
wrote:
> you need poky to build QEMUs and toolchains
>
You should just need *OpenEmbedded* to build the qemus and toolchains. Why
does zephyr.conf include poky.conf? I'd say that any variables that are
useful - such as using the Yocto source mirror
you need poky to build QEMUs and toolchains
> -Original Message-
> From: Philip Balister [mailto:phi...@balister.org]
> Sent: Monday, December 12, 2016 2:19 PM
> To: Bystricky, Juro ; yocto@yoctoproject.org
> Subject: Re: [yocto] meta-zephyr layer
>
> Does t
Does that work without poky?
Philip
On 12/12/2016 02:15 PM, Bystricky, Juro wrote:
> There is interest in the community to support building Zephyr images
> ( https://www.zephyrproject.org/ )in Yocto via bitbake recipes.
> AFAIK the only way thus far to build Zephyr images is based on command
>
