There is no limitation like that, but it's quite easy to break that, you mentioned some ugly BSP before, I wouldn't be surprised if it's broken there. What worked well for me over the years is using

Hello, I am building the xen minimal image using yocto warrior ("bitbake xen-image-minimal") by giving the target machine as "raspberrypi4". It reached 99% but at last I got below error and the whole

Hello, I built the image for Raspberrypi3B+ board. But when boot the board gcc, apt, sudo were not there. Actually only the poweron and poweroff and few basic commnds like, ls, mkdir, whoami were

Hi, Thanks for the input. Regarding docker we are building the docker image and we are using the same image for all nodes so should they not be identical when the nodes start the

Hi, We do something similar except we rsync a sstate mirror to build nodes from latest release before a build (and topic from gerrit are merged to latest release too to avoid sstate and build tree

The recommended set up is to use r/w NFS between build machines, so they all contribute to the cache directly. And yes, if the inputs to the task are identical, then there should a cache hit. If you

Hi, This is maybe more related to bitbake but I start by posting it here. I am for the first time trying to make use of a distributed sstate cache but I am getting some unexpected results and wanted

I read the codes about sstate_cache. Let me briefly talk about how it work . I am not sure if it is right. Example,we have setscene tasks A_setsscene, B_setcene. and Task C ,D are not setscene

Right, Looks good to me since Alexander cleaned-up the AUH after some tinfoil improvements, he is the new maintainer :). Cheers, Anibal

Hi, Thanks for all the efort that has gone into Yocto, esp the documentation. I've setup a new machine definition (x86_64 arch), custom BSP, custom kernel and image. Initially I had trouble

Thanks for the idea of using BBPATH. my change is kind of custom and I don't think someone else will make use of it. Cheers

aside from whether there is a good way to do this, this seems to be a really bad idea since recipes that inherit what they *think* is the systemd class file will be getting something different;

Current Dev Position: YP 3.2 M1 Next Deadline: YP 3.2 M1 build date 2020/6/16 Next Team Meetings: Bug Triage meeting Thursday May 28th at 7:30am PDT (https://zoom.us/j/454367603) Monthly Project

Hi Ayoub, BBPATH[1] is what's used to locate bbclasses. It's defined in your conf/layer.conf. You can either make sure your layer is parsed before the one having the original systemd.bbclass (in

Hi, I would like to make changes on systemd.bblcass in my layer. I can create new one e.g my-systemd.bbclass to overwrite the default one but this will not work since I want that ALL recipes in all

I think my problem is that the do_image_* are running as fakeroot/pseudo. Is there a way to run this task as a normal local user. I read that I should create the socket when not running under local

Hi, thanks for the reply - I've put it in the bblayers.conf - working. cheers, Thomas

All, The below were the owners of enhancements or bugs closed during the last

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on