openembedded

问题 I am trying to update the recipe for zbar from 0.10.0 to 0.20.1. Here is the original recipe: https://github.com/openembedded/meta-openembedded/blob/master/meta-oe/recipes-support/zbar/zbar_0.10.bb My modified recipe is at the bottom of this question. The package does compile, but the problem is that something happens during the "packaging" step and the "work" directory is wiped out except for the "temp" directory inside the "work" directory. During compilation, if I list the files in the

问题 I have two different images which use a lot of common packages. One of them is the wpa-supplicant, which provides a file wpa_supplicant.conf installed by the default recipe. However, I want my own wpa_supplicant.conf to be installed. I have this solved by having a .bbappend in my layer. But now I only want this append to be applied when I compile one of the images, but not the other. In short: is there a way to enable/disable a .bbappend depending on the image compiled? NOTES: I have seen

问题 Is it possible to run a command in a recipe as if it were run on the live system? If so, how? I want to import my key(s) into gpg before the image is created so I don't have to log onto the system after formatting the SD card. 回答1: I found a solution that involves specifying a post install script that runs when do_rootfs is called. All I added to my recipe which installs my public key on the system is below: pkg_postinst_${PN}() { #!/bin/sh if [ -n "$D" ]; then OPT="--homedir $D/home/root/

问题 Is there a way I can ship more files when building an out of tree kernel module? I have tried something like this: FILES_${PN} += "${bindir}/my_program" do_install_append() { install -d ${D}${bindir} install -m 0755 ${D}/my_program ${D}${bindir}/my_program } And like this: FILES_kernel-module-${PN} += "${bindir}/my_program" do_install_append() { install -d ${D}${bindir} install -m 0755 ${D}/my_program ${D}${bindir}/my_program } But still complains: ERROR: QA Issue: my-module: Files

问题 I'm trying out yocto (2.0, jethro) and I want to build an image starting from core-image-minimal . This works fine. Every website out there mention modifying the file build/config/local.conf with (some of) my customization. For example, the target machine (through MACHINE ) or some global settings (through EXTRA_IMAGE_FEATURES ). I also need to modify some specific packages and the way to do it is to create a custom layer. So far so good. What I don't understand is how to "save" all my

问题 How to install command locale & localedef for my image in the yocto project? I have try the following: IMAGE_INSTALL_append = " glibc-locale" But it does not work. How can I do it? 回答1: locale is in a package called glibc-utils and localedef is in a package called localedef . Thus you can add these to your image by doing the following: IMAGE_INSTALL_append = " glibc-utils localedef" BTW I found these packages using the following command (there are other ways, but this will work if the package

问题 Introduction I have a do_install task in a BitBake recipe which I've written for a driver where I execute a custom install script. The task fails because the installation script cannot find kernel source header files within <the image rootfs>/usr/src/kernel . This script runs fine on the generated OS. What's Happening Here's the relevant part of my recipe: SRC_URI += "file://${TOPDIR}/example" DEPENDS += " virtual/kernel linux-libc-headers " do_install () { ( cd ${TOPDIR}/example/Install ; .

问题 Because of old Das u-boot from HEAD branch that do not have gcc 5 yet, I am planning on using gcc 4.8 or 4.9 as a default compiler instead of 5.2. GCC required virtual/libc glibc-2.22. glibc-2.22 complied successfully with 5.2. Unfortunately, it failed at do_compile with the error: ld: cannot find -lgcc with gcc 4.8 and 4.9 arm-poky-linux-gnueabi-gcc -march=armv7-a -marm -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --sysroot=/yocto/hio-jethro/build-hio/tmp/sysroots/hio

问题 I have been working on building customized kernel image using Yocto build system.Now I wanted to change a file /etc/limits/ before I start my build but when I try to find this file "limits",could not find any file name limits and come to know this file is generated after build. I was expecting to find this file(before build) somewhere in meta directory just like file named "profile" is there in poky directory. Now my question is how yocto build system generates this file /etc/limits file

问题 I am trying to get a very simple recipe to build using bitbake, and I cannot figure out why opencv cannot be included. All the example I have found use this setup and appear to have no problem linking against opencv. I am fairly new to bitbake, and fear I am be misunderstanding something very simple. Thanks in advance for any help you can provide. Recipie: UMMARY = "Hello" SRCNAME = "Hello" depends += "opencv" LICENSE = "PSF" LIC_FILES_CHKSUM = "file://${TOPDIR}/Yocto/Recipies/LICENSE.txt;md5