Hi team , while compiling a package i am getting following error :- Log data follows: | DEBUG: Executing python function extend_recipe_sysroot | NOTE: Direct dependencies are

I've been thinking about this and the reason I've not done this is release builds. I'm wondering if we we can somehow make the trigger release build specific. I think is is possible to do this, I've

Sure, I sent a patch for that. Alex

Those are run on a separate schedule, and in context of a-full only cause delays due to queues forming for single available workers. Signed-off-by: Alexander Kanavin <alex.kanavin@...> ---

I've been wondering about this but I suspect we should drop them from a-full instead... Cheers, Richard

The same builds are included in a-full, so they tend to get queued up and cause delays in builds completion, as there's only a single worker allocated to them. Let's run them less frequently to

bitbake mc:target1:target mc = qualifier keyword used to identify a multiconfig build by bitbake target1 = name of multiconfig ( e.g. first machine ) target = Firmware image name to be built for

<vaijayanthi.muralidharan@...> wrote: what is your failing recipe called (exact name )

Anwering my own post now. Am Sa, 7. Nov 2020, um 14:53, schrieb Manuel Wagesreither: I just realized there is 'poky/documentation' which holds the documentation source code. Didn't see that before.

Hello all, I would like to set up Yocto to build my application and produce - an tarball fit to get `docker load`ed, - an image fit to run in qemuarm, - an image fit to run in qemux86-64, - an image

Hello all, I'm trying the become acquainted with the multiconfig feature. I read the relevant chapters in the BitBake User Manual, but some questions I have suggest I did not yet get the whole

whats the name of your recipe ? secondly hping3 requires libtcl8.6.so seems to be troublesome because its asking for devel package not the original library, I wonder why, can you find out the linker

Hi, I am using devtool add hping3 https://github.com/antirez/hping to add hping3 as part of our custom image. Here is my recipe: # Recipe created by recipetool # This is the basis of a recipe and may

adding BBCLASSEXTEND = "native" in lapack recipe will give me another error ERROR: Nothing PROVIDES 'gcc-runtime-native' Is there a another way to make lapack native

right, add BBCLASSEXTEND = "native" in lapack recipe and fix the needed bits to get it going.

Hi, I am compiling scikit-learn python package for arm board but I am facing below errors william@william:~/sagitta/build-as371$ bitbake python3-scikit-learn Loading cache: 100%

I am sorry , I will explain in detail. so what I required is that my python3 binary should be present in both recipe-sysroot and recipe-sysroot-native both as I need to build some python packages

The python3 build for target doesn't directly depend on python3-native. Some recipes do depend on python3-native (although by definition there is a python3 on your host) as they need to run

Howdy! Am Fr., 6. Nov. 2020 um 09:23 Uhr schrieb <william.jacob@...>: I'm sorry, but I don't really understand the question. You say you want python3 crosscompiled. This will happen if

Hi, I am trying to compile python package for yocto and I found python3 (python3.7) is build native then it cross compiled.I want to know why it is done like this in python. Basically I want