Hi, I have two images recipes, one is included in another image recipe: $ ls recipes-core/images ex-image1.bb ex-image2.bb $ cat recipes-core/images/ex-image2.bb include ex-image1.bb ...... My

If the Wm_config instance contains a non-NULL pointer in its kbd_conf_file member, then (in a build that does not use gconf) keys_load_config() will assign that pointer to a local conf_path variable.

Hello everyone, I started to build kernel with initramfs, and so far all that works great. I got my new shiny zImage-initramfs--4.1.14..xxx.bin. I can boot it over tftp, its does exactly what i

It probably will, yes (I didn't test, but it drops a patch that's apparently needed in 0.19). Alex

Ping on this and the following patch. -- Paul Barker

Ping. -- Paul Barker

<alex.kanavin@...> wrote: I've applied this to master-next, we can pull up master once the oe-core patch lands. I'm assuming this will break the current master AB builds if it's applied to

You have to write recipes, then. Please see: https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#new-recipe-writing-a-new-recipe (And keep the threads on-list please.) Greetz --

On Fri, Nov 29, 2019 at 03:56:41AM -0800, keyurthumar0402@... wrote: There is a lot of things confused in here, it seems. > I Have built yocto image for raspberry pi. Ok. Congratulations! >

I Have built yocto image for raspberry pi. It is debian based and apt is already installed. What should i write in source.list ? As I don' t have my personal repository please suggest some standard

On 29.11.2019 11:01, Diego Santa Cruz via Lists.Yoctoproject.Org wrote: I'm currently using meta-tpm from meta-security for tpm2-tools. My reasoning was that this one will likely

Dear all, I got the feedback below by private email (was meant to be sent to the m-l), so I think I’ll go with meta-tmp2 from meta-secure-core for now. But I may switch to meta-tpm from

Drop backported patch (new gettext includes the updates). Drop version from the .bbappend (hopefully no version-specific tweaks will be needed going forward). Signed-off-by: Alexander Kanavin

My finding is: ...only if *artifacts* (also) includes a rootfs. The image class dependency on rootfs seems very hardcoded. I cannot create a recipe that works without *creating* a rootfs. (even though

Hello, I'm getting the following error when I have tried to simulate the image on QEMU adminuser@verathon:~/poky/build$ runqemu qemux86 runqemu - INFO - Running MACHINE=qemux86 bitbake -e... runqemu -

<holzmayr@...> wrote: Yes, up to there everything is clean and nice. And I understand I can build multiple images. I have used this feature since 2006. My point is, that we do not

Of course it does. If you have set DISTRO and MACHINE, you can bitbake core-image-minimal bitbake core-image-x11 bitbake ... whatever image. Thats exactly the point of the MACHINE / DISTRO / IMAGE

So let's then consider the case that the WKS is machine specific. I am fine with that. - Does Yocto support building multiple images from one configuration? - (How) can I build multiple WIC images

Au contraire :) It is the real issue because neither 1) nor 2) is the correct way, and I pretty much explained why that is. What you actually describing are two combinations of image+machine

Dear Josef, I've managed to run build command to generate OS image for the target, which is core-image-sato by executing the following command: $ bitbake core-image-sato Can I know how to proceed