Oh and: anywhere where INCOMPATIBLE_LICENSE is mentioned in the docs, it must be adjusted to stress that per-image variant of it is a far better option than a global ban. Also further instructions and

#gplv3

For what it's worth, I have eliminated meta-gplv2 from the infotainment stack (e.g. a major build) of a major car OEM, so this is doable. It would help if you bring up specific issues that you see and

#gplv3

<poberauer=yahoo.co.uk@...> wrote: The suggested way nowadays is to set INCOMPATIBLE_LICENSE only for the image that is actually going to ship in a product, then work your way throg

#gplv3

<michael.opdenacker@...> wrote: The middle section is actually copied from documentation (I didn't even bother to remove the markup :) If you can find appropriate spots for the first and last

You can simply open the recipe file for core-image-rt (in poky/meta) to see what it does. The realtime-ness (of any image) is set by setting PREFERRED_PROVIDER_virtual/kernel to the realtime flavour,

#patch #yocto #qemu #dunfell #linux

The log file seems truncated? To enable the standard rt test, use TEST_SUITES:append = ' rt' as seen in https://git.yoctoproject.org/yocto-autobuilder-helper/tree/config.json#n1138 and build core-imag

#patch #yocto #qemu #dunfell #linux

It helps if you show log.do_rootfs for the image, so it's possible to inspect what actually got installed into it. Alex

#patch #yocto #qemu #dunfell #linux

That depends on what is your target. If you're running qemu on a x86 host, it's better to not do software emulation and build for qemux86_64 as well, and then run qemu with kvm, so it executes directl

You might want to try enabling gallium-llvm only for the target mesa: PACKAGECONFIG:append:x86-64:pn-mesa = ' gallium-llvm' Alex

You need to build mesa, not mesa-native. And please show exact changes you made. Alex

Try latest poky master? Alex

The following works for me. I get tmp/work/core2-64-poky-linux/mesa/2_22.2.0-r0/packages-split/mesa-vulkan-drivers/usr/lib/libvulkan_intel.so tmp/work/core2-64-poky-linux/mesa/2_22.2.0-r0/packages-spl

I think for software vulkan you need to pass in -Dvulkan-drivers=swrast when building mesa for the target. Alex

I would first check whether any of that work in the branch has meanwhile landed upstream. The post is from 2021. Have you tried the software Vulkan in the guest? Alex

You need to clarify what you want to do exactly. Why can’t you use the existing recipe? Alex

Do keep in mind that PARALLEL_MAKE can and should be set per recipe, so you can make-limit only the worst items. Alex <Oliver.Westermann@...> wrote:

Anything written in C++ tends to consume 1-2 Gb of ram per compiler process. If that lands you in OOM, you probably should limit that with PARALLEL_MAKE:pn-nodejs, but otherwise that is the sad realit

TL;DR version =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D If you want to get everything needed to run a yocto build: - clone the bootstrap repository (ask your distribution maintainer where = it is): $ gi

vulkan-samples recipe is simply using the standard cmake installation routine from cmake.bbclass, so all questions should be aimed to upstream. And upstream doesn't want you to run installation at all

I finally got a moment to look at this. The binary with the samples is being built (you can find it in $WORKDIR/build/app/bin/x86_64/vulkan_samples), but is not installed. So if you want to get it pac