Hi Riko,
Sorry for this confusion.
You can see used wks file
On Fri, Aug 18, 2017 at 07:56:46PM +0800, Riko Ho wrote:
> I'm confused, what is wks ? what layers do you want to know?
Sorry for the confusion. You can read about wic and wks in the
documentation:
To understand which wks file was
On Sat, Aug 19, 2017 at 10:08:06AM +0800, Riko wrote:
> Is it related with :
>
> https://stackoverflow.com/questions/43211384/how-to-get-to-menuconfig-for-u-boot-in-yocto-environment
>
I don't think so. It's about kernel build configuration.
> ?
>
> Thanks
>
>
> On 18/08/17 16:58, Ed Bartosh
On Sat, Aug 19, 2017 at 10:31:32AM +0800, Riko wrote:
> When I did fdisk -l here was what I got :
>
> Disk /dev/mmcblk0: 14.6 GiB, 15640559616 bytes, 30547968 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 b
> it is working then, unless the .deb is removed from download directory. Maybe
> i´m missing something inside the .bb ?
>
Unpacking .deb packages can be done by including
do_unpack[depends] += "xz-native:do_populate_sysroot \
tar-native:do_populate_sysroot \
Hi
It seems that it's not possible to set a custom pre/postinst function for a
kernel recipe.
kernel.bbclass overwrites the necessary variables without checking its content.
My patch does fix this.
However, I'm not sure how to handle similar variables which get overwritten by
kernel.bbclass, ther
If a recipe sets a custom pre/postinst function for kernel-image, this
function gets discarded, which means there is no possibility to set a
custom pre/postinst function.
We check if there is a custom pre/postinst function and only set the
default function if nothing is set.
Signed-off-by: Oliver
Current Dev Position: YP 2.4 M3
Next Deadline: YP 2.4 M3 Cut off is Aug. 21, 2017
SWAT team rotation: Juro -> Paul on Aug. 18, 2017.
SWAT team rotation: Paul -> Todor on Aug. 25, 2017.
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
·We’ve discov
Wow, thanks Chris and Andre!
I'm just getting to play around with this, but Andre's trick seems to have
worked exactly like I was hoping for. I ended up just adding a bbappend
that removes the file touched in the line of the eudev recipe Andre
referenced.
Thanks again,
Aaron
On Fri, Aug 18, 201
A release candidate build for yocto-2.3.1. is now available at:
https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.
Please begin QA on this build as soon as possible.
Build hash information:
meta-intel : 16aea09d224f3ed2021623d17c3e807f4b8ff18d
meta-qt4 : 88989ae3abe98b30089e7518d3a
Hi
This mail is kind of strange, artifacts are not published, there are not rc
specified and afaiu we worked on QA for pyro 2.3.1 last month.
Can anyone clarify this?
Regards,
José
-Original Message-
From: pokybu...@fedora25.yocto.io [mailto:pokybu...@fedora25.yocto.io]
Sent: Mond
On Mon, 2017-08-21 at 12:03 -0700, Perez Carranza, Jose wrote:
> This mail is kind of strange, artifacts are not published, there are
> not rc specified and afaiu we worked on QA for pyro 2.3.1 last
> month.
>
> Can anyone clarify this?
The eSDK artefacts in 2.3.1 were broken and its had to be
Hello,
I re-build YOCTO 2.2.2, trying to set smart (rpm manager for YOCTO). And I
did this successfully. It worked.
It did NOT work on Pyro, which is YOCTO release 2.3 and 2.3.1. Lurking for
the solutions, I found that smart was replaced by DNF in Pyro (2.3). I
finally run into freenode YOCTO IRC
12 matches
Mail list logo