Hello , To create a service in the rpi , do I need to create a new recipe for it, or can I just create it on the rpi directly, m trying the next method now but as I searched I found that they created

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

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

Yocto Technical Team Minutes, Engineering Sync, for August 31, 2021 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == disclaimer == Best efforts are

Yocto Technical Team Minutes, Engineering Sync, for August 24, 2021 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == disclaimer == Best efforts are

<matthias.klein@...> wrote: I completed testing and the commit is in the group I sent to the list for review earlier today. If there are no objections I'll send a pull request early next

Hello, I usually burn hddimg on a usb flash drive and use this usb flash drive to install yocto on my system. Now we have few systems deployed which are non-yocto. They can PXE boot. I wanted to use

Hello Steve, Can you push the commit to the dunfell branch, or do I need to open an official bug somewhere, or what is the correct procedure? Best regards, Matthias -----Ursprüngliche

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Alex, Bruce, Joshua, Randy, Richard, Ross, Saul, Stephen, Steve, Tim, Trevor ARs: N/A

Hello Steve, yes, that commit resolves the issue. Best regards, Matthias -----Ursprüngliche Nachricht----- Von: Steve Sakoman <steve@...> Gesendet: Donnerstag, 2. September 2021 16:09 An:

<matthias.klein@...> wrote: It appears that dunfell also should have: https://git.openembedded.org/openembedded-core/commit/?id=bc4ee5453560dcefc4a4ecc5657df5cc1666e153 Could you see if this

Hello, the following commit needs the variable SDK_BUILD_PATH which doesn't seem to exist in the dunfell branch:

Signed-off-by: Ross Burton <ross.burton@...> --- config.json | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/config.json b/config.json index 5dda653..bee5350 100644 ---

I think you need to move the recipe from a workspace to the layer first with 'devtool finish'. When the recipe is in a workspace, it's taking the source code from the workspace as well, and additional

Hello. I created a recipe with the following command: $ devtool add mosquitto https://mosquitto.org/files/source/mosquitto-2.0.11.tar.gz i got the file: ivr@home-machine:~/work/yocto/build $ cat

Hi Matthias, Sorry for my quick and a bit oversimplified response. I did my first build on an older version (3.20) where ubxtool was not built but present in the repo root. I see now that in 3.23

please use https://github.com/riscv/riscv-openjdk fork.

ensure that you are using same release branches for all layer repos generally RDEPENDS and RRECOMMENDS should be replaced with RDEPENDS_<pkgname> etc.

Hello Peter, I'm not sure it's that simple. To me it looks like the recipe has bugs in python area, or my environment / build is causing problems. In the log.do_compile file I see messages which

hi sir i am trying to build openjdk on riscv but i am facing problem can you suggest what steps i need to follow root@exaleapsemi-3:~/abhi/jdk# bash configure configure: Configuration created at Thu