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:

(re-adding list) Am 27.08.2021 um 11:17 schrieb Ivan Riabtsov: again, any particular reason why you're poking the recipe by hand instead of just using devtool (which perfectly works in this case)? it

Howdy! Am 27.08.2021 um 10:10 schrieb Ivan Riabtsov: if thats all of the recipe, then nothing will be built. you probably want to include at least the class for the buildsystem that you need, for exam

Howdy! Am 07.08.2021 um 02:25 schrieb John Klug: From first glance, I'd guess that the approach is just not correct. If that thing to be fetched also needs to go *into* the image: make it a recipe on

Howdy! Am 08.08.2021 um 16:11 schrieb chiefsleepyeye@...: http://layers.openembedded.org respectively for you http://layers.openembedded.org/layerindex/branch/master/recipes/?q=hotplug obviously

Howdy! Am 29.06.2021 um 01:28 schrieb Jonas Vautherin: Yocto chant #1 applies: "Recipe data is local, configuration data is global." Means: the recipe does not see at all which image it is being built

Leon Woestenberg <leon@...> schrieb am Do., 17. Juni 2021, 14:17: The esdk is meant for exactly that use case.

Am Di., 30. März 2021 um 05:22 Uhr schrieb anthony.l via lists.yoctoproject.org <anthony.l=axxin.com@...>: Please see https://www.yoctoproject.org/pipermail/poky/2016-January/010357

Am Di., 16. März 2021 um 10:49 Uhr schrieb Nicolas Dechesne <nicolas.dechesne@...>: Or grab a beer and start bingewatching https://www.youtube.com/playlist?list=PLD4M5FoHz-TxMfBFrDKfIS_GLY25Qsf

(re-adding list as this certainly does not contain sensitive information - others might add other opinions and hints, as well as my answer should be available for everyone to find it.) Am Mo., 22. Feb

#python