bitbake

Yocto Image file size reduces after adding a particular package

穿精又带淫゛_ 提交于 2021-02-10 19:52:36
问题 I built a core-image-sato image with the following configuration: MACHINE = "intel-core2-32" The generated image size is nearly 1.2 GB. After i add "x11vnc" package, the size is reduced to 380 MB. This image doesn't boot successfully on the hardware. Why is the image size reduced instead of increasing How can we debug what is going wrong? 回答1: The core-image-sato image you use inherits core-image.bbclass, which sets a default value of IMAGE_INSTALL using the ?= operator. This means that if

How to enable tc command when building a kernel using Yocto recipes

三世轮回 提交于 2021-02-10 14:56:19
问题 I want to enable tc command that comes in iproute2 on my linux kernel. My kernel is built using yocto and bitbake. So, I copied the iproute recipes and whole directory from the following link to try -- https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-connectivity/iproute2 And included in my yocto build. That picked up recipe and built it all well. But I tc command is still not available on the built kernel. Question: What am I missing and how to enable tc in the kernel of a linux

How to enable tc command when building a kernel using Yocto recipes

a 夏天 提交于 2021-02-10 14:54:19
问题 I want to enable tc command that comes in iproute2 on my linux kernel. My kernel is built using yocto and bitbake. So, I copied the iproute recipes and whole directory from the following link to try -- https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-connectivity/iproute2 And included in my yocto build. That picked up recipe and built it all well. But I tc command is still not available on the built kernel. Question: What am I missing and how to enable tc in the kernel of a linux

Yocto Bitbake Glibc build fails

那年仲夏 提交于 2021-01-29 10:08:01
问题 I'm trying to build a Yocto image but the build fails when compiling glibc. If I run just bitbake glibc -c compile I get a compilation error as follows: /usr/src/debug/glibc/2.27-r0/git/nptl/pthread_atfork.c:51: undefined reference to `__dso_handle' | /media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi.gcc-cross-initial-arm/../../libexec/arm-poky-linux-gnueabi.gcc

Configuring the bootloader with `fw_env.config` and `CONFIG_ENV_OFFSET`

佐手、 提交于 2021-01-29 07:10:39
问题 I have a previously built image where the content of fw_env.config is (using u-boot): /dev/mmcblk0 0x400000 0x4000 /dev/mmcblk0 0x800000 0x4000 Do I understand correctly that this tells u-boot the partition layout? That is the layout that I would like to have also on a new image. I have a libubootenv\%.bbappend which is supposed to copy the layout above into the new image's fw_env.config (even though I didn't come to the point, yet to test if that actually worked). There are also u-boot

Yocto: Difference between CORE_IMAGE_EXTRA_INSTALL and IMAGE_INSTALL

旧街凉风 提交于 2021-01-28 06:03:20
问题 Recently, i tried to include open source package (iperf3) to target image via Yocto build. (Updating local.conf for IMAGE_INSTALL += "iperf3" , as the project already corresponding recipe). But the final image did not include in root file system. I tried the same by adding to package group recipe in /recipe-core/packagegroups/RDEPENDS_packagegroup* and was able to include it successfully. Can someone provide me explanation for the behavior. 回答1: When you write IMAGE_INSTALL += "iperf3" in

Yocto bitbake configuration for MACHINE variable via shell environment variable

自古美人都是妖i 提交于 2021-01-27 17:54:07
问题 Building via Yocto Project,Which variable will be preferred or picked by bitbake for MACHINE ,environment variable or as set in local.conf 回答1: The answer as usual with bitbake is "it depends" but usually in the case of MACHINE, the environment variable wins. The preference depends on how the configuration file sets the variable. Typically MACHINE is set with soft assignment (e.g. MACHINE ?= "intel-corei7-64" ) and soft assignment will not override a environment variable. A normal assignment

bitbake do_rootfs install fails with shared library symlink in bbappend

纵饮孤独 提交于 2021-01-27 17:11:59
问题 I am trying to add a shared library package to a Yocto Krogoth image from a custom recipe that is dependent on libudev.so.0 but the openembedded-core layer's eudev recipe only provides libudev.so.1.6.3 and a libudev.so.1 symlink: libudev.so.1 -> libudev.so.1.6.3 I have added a eudev_%.bbappend recipes_core recipe that creates the symlink do_install_append() { ln -srf ${D}${base_libdir}/libudev.so.1 ${D}${base_libdir}/libudev.so.0 } and I can confirm the libudev.so.0 file is added to the

using EXTRA_OECMAKE doesn't have any effect in cmake variable in bitbake recipe

元气小坏坏 提交于 2021-01-27 12:05:34
问题 I wanted to add my application in a yocto Image and I used this recipe: DESCRIPTION = "my application" SECTION = "examples" LICENSE = "CLOSED" PR = "r0" DEPENDS += "opencv" SRC_URI = "git://address/to/myApplication.git;protocol=https;tag=v0.1" inherit pkgconfig cmake after running bitbake my-application, I faced this error: fatal error: string: No such file or directory #include <string> I searched on the internet and I found that I need to pass this variable to my CMake in my recipe: EXTRA

Errors including shared prebuilt libraries in petalinux

时光怂恿深爱的人放手 提交于 2020-12-12 11:36:52
问题 I'm trying to simply include a couple of shared libraries to my petalinux project (Yocto based). Following the "Including Prebuilt Libraries" section on pg 65 of the petalinux guide I've got the next recipes to included both libraries (only I post one because the other is the same but only changing the name): # # This file is the libpiimager recipe. # SUMMARY = "Simple libpiimager application" SECTION = "PETALINUX/apps" LICENSE = "MIT" LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5