Hi, i have built an image for the raspberrypi4 but i am not able to find libc.a file in /usr/lib and due to which i am getting an error w.r.t. static linking I am attaching the error which i am gettin

#sdk #yocto #linux

Hi, I am having trouble generating the SDK for my image after upgrading from sumo to zeus. Here is an extract of my log.do_populate_sdk : NOTE: Running intercept scripts: NOTE: > Executing update_gio_

#sdk #yocto #toolchain

The hint regarding bitbake -e showed me the right direction... Within create_shar() function, sed is being called with the SDK_TITLE variable among others. Examination of the SDK_TITLE variable showed

#sdk

are there any aliases etc. to common programs like install in your environment ? maybe do bitbake -e my-image and inspect the output especially do_populate_sdk function and see if you find some sed cm

#sdk

Hello Yocto Community, I am new to the Yocto Project and need some help regarding creating the SDK installer for my image on a Ubuntu 18.04 host machine... So far I was able to build an image for my t

#sdk

Hello, I created an eSDK and I am installing it on a docker image I created. Using the devtool I added/created a recipe for a simple HelloWorld application (such application is located in github, but

#yocto #sdk

Hello Khem Raj, Sorry for the late reply. I was not available during last week. So, I post here my recipe. But before I want to make two comments: I found a variable in the cmake\*.bbclass (i.e. OECMA

#sdk #yocto

please post your recipe > > >

#sdk #yocto

Hi, I built an eSDK. Now I'm using devtool add to create a hello world recipe. Once the recipe was in place, I added some cmake optoins via EXTRA_OECMAKE in htis way: EXTRA_OECMAKE += "-DCMAKE_FIND_RO

#sdk #yocto

Hi Joris, Thanks for reporting the issue. I can't test this right now. Can you reproduce the problem with just oe-core and a core-image that is similar to yours? If you can, then please either debug t

#sdk #toolchain

Hi all, I am developing a custom distribution based on poky and I am creating an extensible sdk from my image, but when I install this extensible sdk, I find an error in python3 and an error in reloca

#sdk #toolchain

Hello, I am trying create an eSDK from the meta-ivi layer. In order to do so, I had to create some .bbappend files to make some recipes extend to the nativesdk class. Particularyl I created the follow

#sdk #yocto

Hello Raj, and thanks for your help. I actually found out that my problem seems to be that the files of one of the dependency packages are not staged into ./build/tmp/sysroots-components/x86_64-native

#sdk

<j.armandohernandez.j@...> wrote: check DEPENDS how are they specified in recipes, it might get overwritten in some cases for extended recipes if overrides are in use on depends. Secondly, check

#sdk

Hello, I have two recipes (let's call them "recipe-A" and "recipe-B"). Both recipes extend the nativesdk class. recipe-B depends on recipe-A When building both recipes for target, everything goes well

#sdk

Hi, Thanks for this explanation! Hmm. I would rather see FOO_append += "bar" being used every time when spaces are expected. It's way too easy to forget the extra space which causes annoying and hard

#sdk #systemd

I agree it's a bit confusing at first (I was doing the same long time ago, before bitbake -e was even showing the history of evaluation), but everybody who uses bitbake often should learn this simple

#sdk #systemd

Yes, quite likely. Tough reason why += doesn't work is a mystery to me :) I hack things until "bitbake -e" shows the right things for the recipes. -Mikko

#sdk #systemd

Hi, (lets keep this on the list too) You can add _class-[target|native|nativesdk] to all variables to override defaults. Verify with "bitbake -e". Hope this helps, -Mikko

#sdk #systemd

> DEPENDS_class-target += "systemd" You surely meant DEPENDS_append_class-target = " systemd" here

#sdk #systemd