Hello all you Open, Embedded, and even OpenEmbedded people out there! This is your gentle reminder that we are hosting an OE Workshop in Brussels on Monday, February 6th - the day after FOSDEM at Aven

Is it maybe the restricted network access thats biting you? See third item: https://docs.yoctoproject.org/migration-guides/release-notes-4.0.html#new-features-enhancements-in-4-0

It can always be added if is is found useful and robust. We tend to be careful about taking things into core layers as long as those two concerns, plus the maintenance commitment are not clear. Techni

For the record - Yocto chant #1: Recipe data is local - configuration data is global. On Thu, Nov 17, 2022 at 4:30 PM Quentin Schulz via lists.yoctoproject.org <quentin.schulz=theobroma-systems.com@li

Again re-adding list.... I encourage you to look at and understand the evaluation for yourself by issuing "bitbake-getvar -r core-image-minimal IMAGE_INSTALL" Greetz, Josef

#systemd

Re-adding list, as I think this is valid information for all Yocto users. No, thats not how it works. Its like this: - if the variable is supposed to only have an effect within the very bb file that y

#systemd

Hi Martin, its Yocto chant #1: "Recipe data is local, configuration data is global." Means: whatever happens in a recipe, other recipes can't see it. Whatever happens in a configuration file (local, m

#systemd

Hi Maik, this is a number of things being mixed up. 1) a recipe cannot affect another recipe. the image is a recipe, sshd is a recipe. so you either can set this in a bbappend to thesshd recipe, or in

Howdy there! We're happy to finally announce the Yocto Project Mini-Summit taking place the day before ELC-E in Dublin! Monday, September 12th, 2022 | 2:00 – 5:30 PM Location: Convention Centre Dublin

Howdy! Am Do., 5. Mai 2022 um 10:43 Uhr schrieb jchludzinski via lists.yoctoproject.org <jchludzinski=vivaldi.net@...>: The BSP that is implicitly used in that video is the generic

As already pointed out on IRC, the only real solution is: a) removing the shipped binaries from the install (as Khem also mentioned) and b) making the module re-build the binaries using the cross tool

Howdy! Just pack a more recent Ubuntu into the container engine of your least dislike - docker usually does the trick well enough if you can go with its license situation, otherwise podman is an inter

Howdy! Karthik Poduval <karthik.poduval@...> schrieb am Mi. 2. März 2022 um 04:23: As a recipe cannot affect another recipe, and image recipes are obviously recipes too, this is usually not usef

Howdy! While that is perfectly true from the pure technical facts, I have to add that building in Parallels on a M1 is ok-ish. You have to crank up the VM way beyond the defaults, to something like 6-

Howdy! The real question is: what is the condition? It must be something that is constant across all of the build. And if can only come from either a .conf file or the environment, otherwise it would

Hi Rayaan, Currently DKMS is not supported in Yocto/OE and there are no imminent plans to change that. See the discussion on the topic at https://lists.openembedded.org/g/openembedded-core/message/159

#dunfell #kernel

(re-adding list) Am 19.11.2021 um 10:11 schrieb lucapirozzi via lists.yoctoproject.org: You have to use the path you found hexdump at. Check in your running target by using "which", or inspect the ima

#yocto

Am 19.11.2021 um 10:02 schrieb lucapirozzi via lists.yoctoproject.org: Check oe-pkgdata-util find-path in your build to find out which package/recipe to actually look at. Greetz

#yocto

(re-adding list as I messed up) Am Mo., 1. Nov. 2021 um 21:45 Uhr schrieb jchludzinski <jchludzinski@...>: MACHINE = "raspberrypi3" (for example, pick your specific one like http://git.yoctopr

Brutally honest: Yes it can. No you won't be able to do it without reading the docs. <donald@...> schrieb am Mi., 13. Okt. 2021, 08:51: