This series adds a recipe for the lvgl sample from zephyr. Due to how meta-zephyr works we need to pull in some additional modules for the build to succeed. The first three patches are just coding

Dear Alexander, The reason for running it in /srv/yocto is because this directory uses NFS caching. I will look into the possibility of running the build in $HOME instead. I have also ran the

Thanks, I got around to looking at this again. For the first issue I agree the rstrip is the best option. For the second, I don't really want to change the on disk signature formats since that will

lists.yoctoproject.org wrote: I'm not sure where this belongs, but maybe you can try to submit it to the meta-oe repository. Look at the readme[1] for instructions. [1]:

Dear Sirs, I have a hard time to cross-compile and to properly include the custom ROS2 foxy package into the Yocto image. I properly added meta-ros layer and ROS2 foxy distro to our Yocto build by

Hello Jonas, I’ve also recently hit an error during thedo_patch task of libselinux. 001-Fix-NULL-pointer-use-in-selinux_restorecon_set_sehandle.patch has been recently added to the dunfell branch

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.3.4.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2.

see https://github.com/agherzan/meta-raspberrypi/pull/935

GitHub has already started "brownouts" for git protocol, which will cause random fetcher failures in builds. Signed-off-by: Tim Orling <ticotimo@...> ---

This patch updates SRC_URIs using git to include branch=master if no branch is set and also to use protocol=https for github urls as generated by the conversion script in OE-Core. Signed-off-by:

bitbake is now warning on git trees not having branches specified, with errors similar to below: WARNING: URL:

I tweaked the recipe a bit (you should use SRCREV, versus a tag), etc, and added some link flags to make things static. This tends to be why I write my own do_compile for go applications, so I can

Sure here you go: ``` SUMMARY = "easyjson" DESCRIPTION = "easy json command util" HOMEPAGE = "https://github.com/mailru/easyjson" LICENSE = "MIT" LIC_FILES_CHKSUM =

Signed-off-by: Khem Raj <raj.khem@...> --- recipes-devtools/flex/flex_%.bbappend | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 recipes-devtools/flex/flex_%.bbappend diff --git

This patch updates SRC_URIs using git to include branch=master if no branch is set and also to use protocol=https for github urls as generated by the conversion script in OE-Core. Signed-off-by:

Well it turns out that following the Perf recipe was not only a good idea, but absolutely necessary. The perf recipe copies the code out of the work-shared kernel directory into the perf build

It varies based on the application, the ones I've dealt with, tend to have a -static flag. Of course, the flag may not be exposed, and in those scenarios, I patch the Makefile/build. If you have

Yep might be… For me that’s desirable as these a built-utils, it’s golang and I see no benefit in having them dynamically linked anyay. Any tips how to statically link these? As far as I

I'd bet it is a variant of this: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14386 Bruce -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the

Here some outputs: Bitbake -c devshell target-recipe sh-4.4# easyjson Segmentation fault sh-4.4# strace