Hi, I am building an AI engine on a gaming motherboard. I chose it for I need a powerful GPU. And I am using Yocto to build a custom OS for this engine. So, at first, what do you think the most approp

#yocto

use meta-intel build for a core-i7 I also have an ASUS ROG board running yocto.

#yocto

Hi everyone. I am trying to setup a Package Feed with signed ipk packages. For this, I first set up the key pair on my build host. This is the result of "$ gpg --list-keys" : /home/<username>/.gnupg/p

#yocto #raspberrypi

see http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.16.3.bb?h=dunfell#n114 change that to -Dfdkaac=enabled if it works, then perhaps tu

#yocto

Hi All, I'm trying to bitbake a recipe for python3-dlib (the python API). Here is the recipe: SUMMARY = "A toolkit for making real world machine learning and data analysis applications" HOMEPAGE = "ht

#yocto #zeus #python

Hello all, I'm starting with the Yocto project (Zeus) and I made some experiments with the kernel recipe. For one of my assignments, I needed a do_kernel_configme task, but it wasn't provided by our k

#yocto #bitbake

Just saw that the issue is that you can't use rootfs-dir with a subfolder as the pseudo folder is missing in the parent folder, ended up using overlayfs

#yocto

Thanks for the suggestion, but they are using the C++ API as well. I already created a recipe for the C++ API of dlib and it is working, the only thing needed is compitling the Python API.

#yocto #zeus #python

According to [1] yes - you might want to consider back porting one of the more recent versions of numpy from [2], as you are using a pretty outdated one [1] https://stackoverflow.com/questions/5466584

#yocto #zeus #python

It looks like you're using OE-Core and nodistro and we generally test the eSDK with poky. It also looks like you're using rm_work and we do not test that with eSDK on the autobuilder. For some reason

#yocto

Hi, I would like to remove hwclock from the rootfs cause we don't have an RTC. Maybe later I'll replace it with fake-hwclock. I'm using dunfell with IPK packages and I tried to add the following setti

#dunfell #yocto

Thanks… I forgot that… linked. I appreciate the help. Steve

#yocto

#yocto

Thanks you...

#yocto #sdk #cmake

Khem: There are at least 4 zeus released tags, can you vouch for one of them to work properly with meta-clang ? Porting to dunfell might not be possible at this time... Would it be possible to build t

#yocto

this is intentional, when you use meta-clang, then llvm is preferred from LLVM since them we have consistent version of llvm for clang and others.

#yocto

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

Hi, Multiple ways to fix this. One is to switch to using dunfell branches for the BSP SW stack, if they are available. Alternatively you can use the old zeus based BSP SW stack but for that you need t

#imx6 #yocto #dunfell #swupdtae #libubootenv

I attempted to add llvm to my zeus image, and I am seeing the following Yocto build error… What is the actual problem here, and how best resolve ? Build Configuration: BB_VERSION = "1.44.0" BUILD_SYS

#yocto #llvm

Hi, I am trying to include qca9377 module in my image (yocto-gatesgarth). I am using command bitbake imx-image-full, and i added two lines in my local.conf file: MACHINE_FEATURES += " qca9377" IMAGE_I

#qca9377 #yocto #bitbake #gatesgarth