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

Hello List, I am making kernel yocto image for imx8mplus. But according to my project requirement i need different audio driver rather then default which comes with this linux image. I am able to see

#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

Hi Yocto community, I run into an issue where I can't use the runqemu command by use of the SDK. It reports the following: "runqemu - ERROR - Failed to run qemu: qemu-system-arm: -netdev user,id=net0,

#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 Praveen, I'm not aware of anyone else doing that. For libraries/recipes, you could just omit certain packages from the eSDK but you don't seem to want to do that. What is your goal in filtering hea

#sdk

I am looking for Custom SDK with filtered Header files/libraries based on some rules/approvals. It means not all files from YoctoSDK will be packaged in the CustomSDK. What is the mechanism or approac

#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

yocto provides a layer to abstract native binaries on top of build host and thats what you are seeing. Its as designed. > > >

#toolchain #sdk #bitbake #native

I'm attempting to create a USB first boot tarball for our custom iMX6 board that would contain the imx-usb-loader executable, config files and u-boot/SPL files. The goal being to deploy that to the pr

#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 Marco, In your opinion isn't enough to ask for eSDK? for instance if i want to add Node-RED, it would be difficult to build with devtool? because i've seen that it doesn't resolve dependencies a

#sdk #zeus #toolchain

With the eSDK i've to use devtool right?

#sdk #zeus #toolchain