Hi, A kernel recipe will provide linux-libc-headers after a "make headers_install" call... So the SRC_URI of linux-libc-headers can be the same as from the linux kernel recipe, or linux kernel recipe

Yes, we're talking about the same thing :) A lot of yocto things don't work well if major changes happen and WORKDIR isn't completely cleaned in between. With various BSP layers things can be even wor

Hi, I know it's not the best or recommended approach, but I find it hard to avoid merging linux-libc-headers recipe with the actual kernel recipe that a distro is using. At least a static copy of some

Hi, When both yocto update and your own changes are modifying the same recipes, then conflicts can occur. If builds are failing, then your environment is breaking something. It might even be the BSP l

Hi, We do SYSTEMD_SERVICE_${PN} = "" a lot but reasons are a lot more complex. To properly tune target system boot, one really needs to fork most systemd service files. This is needed to set cgroups,

From: Matt Hoosier <matt.hoosier@...> Insert an explicit pass to fetch all blobs needed by Git LFS, during the fetch() function. This avoids the default behavior of Git LFS to wait until 'git c

From: Mauro Queirós <maurofrqueiros@...> Function "contains_lfs" was only looking at the master branch when searching for LFS content. LFS may be configured in specific branches only, so we need

From: Mauro Queirós <maurofrqueiros@...> Git-LFS objects were being fetched even when lfs=0 was not set. This patch disables LFS smudging when lfs=0. That way, only the LFS pointers are download

Sorry, third patch needs to be backported from master for git lfs to work nicely on dunfell. Will send a v2. -Mikko

From: Matt Hoosier <matt.hoosier@...> Insert an explicit pass to fetch all blobs needed by Git LFS, during the fetch() function. This avoids the default behavior of Git LFS to wait until 'git c

From: Mauro Queirós <maurofrqueiros@...> Function "contains_lfs" was only looking at the master branch when searching for LFS content. LFS may be configured in specific branches only, so we need

Locally, as developer you always have a local branch where you can cherry-pick changes. With git submodules and repo tooling, you should use a local or project specific clone of poky. Or move all upda

Hi, When backporting changes, I find it better to cherry-pick the changes for e.g. python3 update from master to the old branch that I have to use. In my case I can not update anything which breaks AB

Hi, For those who aren't afraid to digging deeper, it is possible to limit the impact of BSP layers by e.g. restricting which recipes and bbappends get applied in your product via BBMASK in distro con

Hi, I was wondering on same thing few days ago. nativesdk-clang and clang-cross-canadian-aarch64 if your target arch is aarch64 bring a working clang compiler to the SDK. I was also missing the clang-

bitbake -e my-recipe ? Maybe grep for the variable of interest? When adding layers, only way to be sure is to actually review the layers and their bbappends. I tend to BBMASK everything out which I ha

Hi, You can try with SRC_URI_prepend_machine1. Cheers, -Mikko

Hi, Debian developers changed branch names in their repository. Fixed in latest master and dunfell branches so either update or cherry-pick the changes: https://git.yoctoproject.org/cgit/cgit.cgi/poky

Hi, You need to add exceptions to build a lot GPLv3 components but not let them be part of product images. In distro config: INCOMPATIBLE_LICENSE += "GPLv3 GPLv3+ LGPLv3 LGPLv3+" ... WHITELIST_GPL-3.0

Hi, We do something similar except we rsync a sstate mirror to build nodes from latest release before a build (and topic from gerrit are merged to latest release too to avoid sstate and build tree get