You can do the same thing with: do_unpack[depends] += " xorriso:do_populate_sysroot" but note that you want xorriso-native, not xorriso. Cheers, Richard

Hi Mike, lists.yoctoproject.org wrote: I usually search on the OpenEmbedded layer index: http://layers.openembedded.org/layerindex/branch/master/recipes/?q=tailscale Seems like you are right, there

Does anyone know if there is an existing bitbake recipe for building the Tailscale client daemon and CLI tool from the following source? A search on Google yielded no obvious

From: yockgenm <yock.gen.mah@...> Signed-off-by: yockgenm <yock.gen.mah@...> --- classes/zephyr-kernel-src.bbclass | 12 ++++---- .../{qemu_4.2.%.bbappend =>

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.2_M3.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1.

Hi all, I have a need to unpack an ISO image during do_unpack. This does not appear to be one of the extensions that is handled by default, so I am working out a way to use xorriso to do this for

closed you can get is qemuarm64, you can also use package management in image and install/update/remove individual packages. something

A build flagged for QA (yocto-3.2_M3.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.2_M3.rc1 Build hash information: bitbake:

Hi Vijay, I have redirected this thread to the main yocto list. The yocto-builds list is for automated build outputs rather than discussions.

Hello! Generally speaking, at the point when we get to working with boards we are needing to interact with the outside world so we have to run on the target hardware. Once U-Boot (or equivalent) is

Hi, Actually I'm working on the DART-IMX8M board. I can able to build the image in linux machine and run it on the board. But for every build, i have to run the image on board. I have checked on the

It's supposed to be file:// not files:// in the URL. -- Maciej PijanowskiEmbedded Systems EngineerGPG: 9963C36AAC3B2B46https://3mdeb.com | @3mdeb_com

I'm sorry, but you I think you really do need a pair of glasses ;) It's supposed to be file:// not file:// in the URL. -- Maciej PijanowskiEmbedded Systems EngineerGPG:

now there is only one issue has left: ERROR: ExpansionError during parsing /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvdial/wvdial_1.61.bb

Michael Halstead has confirmed this. Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- scripts/auh-config/upgrade-helper.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

I wasn't going to be blamed for the bike shedding of this but as we've gotten started I'll stick my oar in. My suggestion would be meta-mainline-kernel, meta-linux-kernel or

Hi Is it possible to split a rootfs image into two images for two partitions? Let's say I have a rootfs, but I want to split out /usr/local/applicationx into a separate image so that I can have it on

I would suggest calling it something like meta-kernel.org then. Naming something "vanilla" might cause confusion as well. I would recommend maintaining a "kernel-stable" moving target recipe that

Hi folks, After a bit of a break I'm looking again at the meta-kernel layer and I've got some changes planned. I'd like to get some feedback on these from anyone who has looked at or used the

It is the first local file on the list, so this hints that it is probably a file location issue and not a file naming one. Here is your problem: this directory should be named "wvstreams"