I am also facing the same issue while compiling grpc.

#sdk #yocto #toolchain

You can add a kernel config fragment disabling/enabling needed drivers during build and you can either build them into kernel proper or as kernel modules. If you build them as kmods then you have to a

#sdk #yocto #imx8 #kirkstone #kernel

Hi Yocto community, I figured out what happened, hopefully this is useful to anyone. We did use parts from the meta-cloud-service repository, to be specific the meta-openstack. That layer has a qemu_6

#kirkstone #sdk

Hello Everyone, I have generated two build with different platform for same target (core-image-minimal) and for same yocto release "dunfell" . One image I have generated with the help of yocto project

#sdk #toolchain #ubuntu #yocto #linux

Hi, I came to know about the package feed feature, through which we can update the application in the target image by using apt-get commands. I just read about it on following link. https://subscripti

#bitbake #sdk

Hi, I came to know about the package feed feature, through which we can update the application in the target image by using apt-get commands. I just read about it on following link. https://subscripti

#yocto #sdk

That is, can you not package each moduleA as moduleA and moduleA-private using Yocto's packaging mechanism with the *3.h files being in the private packages? I don't work with the SDK very much so I c

#sdk

Hi Yocto Devs, I have this issue when I want to generate a SDK for our custom distro. We require the use of debian package due to historic reasons so the package management has been enabled, where the

#yocto #sdk

Hello everybody, I come today to try to solve my problem. I am building a bsp and sdk for a raspberry pi (MACHINE = raspberrypi4-64) in the form of a compute module. I'm trying to compile this app: ht

#dunfell #qt5 #raspberrypi #sdk #linux

I am unable to build an extensible SDK for my RISC-V machine. Required Details: Also, I am able to build the normal SDK successfully. I ran this for my custom machine "cdac-ooo". MACHINE=cdac-ooo bitb

#dunfell #sdk #yocto

Native recipes are meant for the build machine itself to aid your build. If you are packaging something to run on a destination machine, you should be producing non-native recipe images. ..Ch:W..

#toolchain #sdk #bitbake #native

Hello Enrico, an eSDK would be enough to do everything, however I would demand the entire development system if I were to start a project, but that is my opinion. I don't know well Node-RED but using

#sdk #zeus #toolchain

Hello, I permit myself to contact you because I got a weird issue in my sdk toolchain. So, as I need "qtremoteobjects" in my embedded linux image, I add it like this: ---------------------------------

#toolchain #sdk #qtremoteobjects #repc

this is fine, if you are interested submit it as a patch to include in metadata in meta-python

#sdk

Hello, I wrote a kernel driver which exposes some header to userspace application. Application engineers use generated SDK, so I'd like to export that header file as part of SDK. I added my header to

#kernel #sdk

Thanks you...

#yocto #sdk #cmake

Any one seen this before… ? SDK appears to be working okay without the inclusion of native python3 components, not sure how the inclusion breaks devtool…

#yocto #sdk

No the vivado module sets up key variables, the lib path, and the include paths for building Xilinx low level drivers built into bootapp/kernel... I need to be able to include these components in actu

#yocto #sdk

EXT SDK, aarch64, zeus… How do I best modify the EXT SDK build env so as to reference the “vivado” env dependencies ? Is there a way to build in support so that the “module load” command would be usab

#yocto #sdk

Hi Can you try this patch ( if you are using master ) and see if that helps diff --git a/recipes-devtools/clang/clang_git.bb b/recipes-devtools/clang/clang_git.bb index b8986be..b0c81f1 100644 --- a/r

#sdk #dunfell #yocto #kernel #linux