There's a section about building from source with a patch in the article he linked with his first message. I don't know much about python in yocto, but maybe doing that in a recipe could work?

#bitbake #python

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]: https://git.openembedded.org/m

There's a 'websockets' PACKAGECONFIG for the mosquitto recipe. You can read more about how to change PACKAGECONFIGs in the documentation [1]. Be aware that since yocto dunfell, the websockets PACKAGEC

#zeus

To piggyback on that, it is possible to set Type=oneshot[1] for the service so that systemd considers the service to be up after it exited. I find it useful for init or migration scripts that another

#yocto

There is a recipe for RPi.GPIO available in meta-raspberrypi [1]. I doubt that it's installed in any of the default images. You should add it to your image by appending to the IMAGE_INSTALL variable.

#raspberrypi

I recommend putting your whole python project into a repository (e.g. with git) and then create a recipe that fetches the git repository and installs the files to a sensible location. You should be ab

#python

To backport a newer version, I usually just take the trial and error route by copying the recipe to a custom layer and then, if necessary, resolving missing or outdated dependencies on the go. This wo

In this case you should probably ask your vendor how they set up networking and why they installed both. It's possible that your vendor configured something different than the defaults, hard to tell w

Glad to hear it works. This doesn't sound correct. It's already some time ago that I last worked on networking. As far as I remember, systemd-networkd and NetworkManager are working differently: Confi

systemd-networkd and NetworkManager are two different things. Make sure that you only have one of them running at the same time. A quick solution is to use systemd to disable the systemd-networkd serv

The OpenWRT wiki has a section on porting UCI to different linux distributions [1], but you can probably skip that completely. Searching for UCI in the recipe index [2] yields a result from the meta-o

<snip> Searching for these error messages I found a comment on GitHub [1] which states that this is caused by missing assembly syscall wrappers. Experimental support for RISC-V was added in Go 1.14 [2

#yocto

Hi Alessandro, I never worked with node-red in yocto, so I can't speak specifically for that, but I encountered similar situations before. Here is what I usually do when I need to change a file in a r

Hi all, I recently upgraded my project from dunfell 3.1.5 to 3.1.6 and saw errors about pseudo path mismatches on various build machines. Removing TMPDIR solved the problem, but I did some digging to

Hi Zakaria Probably the image manifest is what you are looking for? From https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#image-generation-dev-environment : The manifest file (.m

#yocto #linux

Are you using vim to edit the files? If yes, then take a look at "backup files": https://vimhelp.org/editing.txt.html#backup Be aware that vim possibly creates swap and undo files, too. https://vimhel

#cm3 #dunfell

lists.yoctoproject.org wrote: This is the official download page for the RT patches: https://wiki.linuxfoundation.org/realtime/preempt_rt_versions There is also a section about which patches are activ

Is your kernel actually configured with cgroups support? You need CONFIG_CGROUPS and many of the child configs. From your error message I suspect you're missing CONFIG_CGROUP_DEVICE, but that's just a

lists.yoctoproject.org wrote: The log indicates that it is missing a dependency which ships "rpc/rpc.h". Some googling turned up this discussion on the openembedded-core mailing list: https://lists.op

#yocto #kernel #zeus

Hi Steve lists.yoctoproject.org wrote: I'm not sure to what lines you refer by "banner", so I just wrote my thoughts to both below. Both are probably produced by getty, either util-linux-agetty or sys

#yocto