[yocto] [ANNOUNCEMENT] Yocto Project 3.1.15 (dunfell-23.0.15) is Released

Hello, We are pleased to announce the Yocto Project 3.1.15 (dunfell-23.0.15) Release is now available for download. http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.15/poky-dunfell-23.0.15.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-3.1.15/poky-dunfell-23.0.15.tar.bz2 A gpg si

Re: [yocto] SSTATE corruption

Alex is very much correct, you should not see corruption. But I think more detail is in order. If your distro repository is a "garden variety" set of image recipes and recipe overrides that pull upstream source bundles, then your SSTATE cache should age nicely from release to release. However, if

Re: [yocto] KERNEL_DEVICETREE cannot be appended?

Hello Alexandre, > Did you try RPI_KERNEL_DEVICETREE:append? No, I was wrong. This also replaces all device trees. Only the overlays are then additionally present. I understand that it is bad practice. However, I would still like to understand why the "append" behaves so strangely. Best regar

Re: [yocto] KERNEL_DEVICETREE cannot be appended?

Hello Alexandre, > Did you try RPI_KERNEL_DEVICETREE:append? Thank you, that works. > You should probably create a new machine, it is a bad practice to change > KERNEL_DEVICETREE from local.conf OK. Best regards, Matthias -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this

Re: [yocto] KERNEL_DEVICETREE cannot be appended?

Hi, On 22/03/2022 17:10:10+, Matthias Klein wrote: > Hello, > > I am trying to add a device tree in a yocto based on the meta-raspberrypi > layer. > Adding the device tree via a patch in a bbapend of the kernel recipe is no > problem. > > But all attempts to add the file in the local.conf

[yocto] KERNEL_DEVICETREE cannot be appended?

Hello, I am trying to add a device tree in a yocto based on the meta-raspberrypi layer. Adding the device tree via a patch in a bbapend of the kernel recipe is no problem. But all attempts to add the file in the local.conf of the variable KERNEL_DEVICETREE replace all other device trees. I.e. o

[yocto] Yocto Project Status WW12`22

Current Dev Position: YP 3.5 M4 Next Deadline: 4th April. 2022 YP 3.5 M4 build Next Team Meetings: * Bug Triage meeting Thursday Mar. 24th 7:30 am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) *

Re: [yocto] SSTATE corruption

No and no. Alex On Tue, 22 Mar 2022 at 14:48, Rusty Howell wrote: > > Is the sstate cache sensitive to different releases and or the ordering of > the bblayers? We are upgrading our Yocto-based distro from dunfell to > hardknott. So for a while we will be building our distro on both release

[yocto] SSTATE corruption

Is the sstate cache sensitive to different releases and or the ordering of the bblayers? We are upgrading our Yocto-based distro from dunfell to hardknott. So for a while we will be building our distro on both releases. Do we need to keep the sstate caches separate for these builds? Another r

[yocto] #bitbake #sdk

Hi, I came to know about the package feed feature, through which we can update the application in the target image by using apt-get commands. I just read about it on following link. https://subscription.packtpub.com/book/virtualization-and-cloud/9781784395186/1/ch01lvl1sec21/setting-up-a-package

Re: [yocto] Strange sporadic build issues (incremental builds in docker container)

It's hard to say without the full error message, and the build directory of the affected recipe. The easy way out is to simply wipe tmp/ before each build. Alex On Tue, 22 Mar 2022 at 09:51, Matthias Klein wrote: > > Hello together, > > I am building various kirkstone/master yoctos every night v

[yocto] [meta-zephyr][PATCH] meta-zephyr-core: drop obsolete patches

These patches are not being applied and not required any more. Already part of zephyr 2.7.1 and zephyr 3.0.0 Signed-off-by: Naveen Saini --- ...0001-cmake-added-missing-file-ext-to.patch | 42 ...rduino-nano-33-ble-storage-partition.patch | 49 --- 2 files chang

[yocto] Strange sporadic build issues (incremental builds in docker container)

Hello together, I am building various kirkstone/master yoctos every night via Jenkins inside a Debian Bullseye Docker container. These are incremental builds, reusing the build directory and sstate-cache of the previous build. The different yoctos are built in order. Each time, a new Docker con