Since uvicorn has a proper pyproject.toml, you will want to use the new "PEP-517" classes available since 'kirkstone' Yocto Project release. You want to look at the pyproject.toml "build-backend" line

#bitbake

This is provided by wireless-regdb https://git.yoctoproject.org/poky/tree/meta/recipes-kernel/wireless-regdb/wireless-regdb_2023.02.13.bb This is provided by linux-firmware-imx-sdma-imx7 https://git.y

#imx6 #kirkstone #yocto #linux #bitbake

use SRCPV in PV as the error says

#bitbake

Hi, I am trying to build an image using kas built tool for ti TDA4VM. For this I have created the attached j721e.yml file. When I put machine as j721e-evm it is showing the below error " Overrides cou

#bitbake #kirkstone #yocto

Federico, Thanks for your reply. I did build a recipe for a tar.gz source archive previously, which worked. But for the RPM I felt like I was missing something. Meanwhile, my multilib build for core-i

#bitbake

Hi Martin, As far as I remember, RDEPENDS is handled by the package manager when installing the package. So I imagine this is a way to make sure that a filesystem is not built with two packages that a

#bitbake

The Suricata recipe Python environment variable is PYTHON_SITEPACKAGES_DIR="/usr/lib64/python3.10/site-packages"

#kirkstone #bitbake

Hi, After applying the patch to the source, I suppose you built the kernel (and is just missing in your email) ? If not that is a quite important step missing ;) Besides that: 1) preempt-rt patch is o

#patch #rpi #yocto #bitbake #dunfell

“This folder is empty” Ross

#bitbake

Hi Michael, google link doesn't work. Without seeing source hard to say what it can be but it looks like typo or so as float numbers use only one '.' ;) Which poky version do you use? Do you use a cus

#bitbake

Hello, I'm relatively new to Yocto and have a question related to bitbake and nodejs modules. I'm working with Yocto Hardknott and would like to integrate a nodejs module into my build. To do so I'm u

#bitbake #hardknott

You need to rebuild the image: bitbake core-image-minimal Alex

#linux #warning #toolchain #bitbake #dunfell

Then you need to check the output of 'env' a) when you start the shell b) when you use oe-init-build-env and figure out how the incorrect variable gets into the environment. Are you using oe-init-buil

#bitbake

Can you try something like this INCOMPATIBLE_LICENSE:pn-foo = "GPL-3.0* LGPL-3.0*"

#bitbake #dunfell

Hi Joshua, It's 100% my fault, I'm mixed 2 variables: ROOTFS_POSTPROCESS_COMMAND IMAGE_POSTPROCESS_COMMAND My "ln " command have to be placed into IMAGE_POSTPROCESS_COMMAND, not ROOTFS_POSTPROCESS_COM

#kirkstone #python #bitbake

I have generated two yocto builds at different times while taking the same SDK and target. So is there any way to verify yocto builds so I could differentiate between them for their timestamp, date an

#yocto #linux #bitbake #llvm #distro

Use exiting DATETIME variable and add it to vardepsexclude if it isn't already there.

#bitbake #os-release

this is nice. I mistook it for the dependencies

#bitbake #yocto

Hi all, I'm trying to debug this issue for quite a while but couldn't get any helpful indication on how to solve it. (In case it matters, the build runs on a docker container with shared volumes for S

#hardknott #bitbake #kernelmodule

Forgot to mention that the build machine is x86_64 and I want to build for target aarch64. This is the generated bitbake recipe: # Auto-Generated by cargo-bitbake 0.3.15 # inherit cargo pkgconfig # If

#bitbake #toolchain #rust #kirkstone