bitbake

问题 I am writing an image description which I want to append on multiple layers a bsp layer, a security layer and an application layer. in bsp: I have image.bb and image-dev.bb with require image.bb on the other layers I have image.bbappend and image-dev.bbappend require image.bbappend does causes the error: ERROR: ParseError in .../sources/meta-application/recipes-core/images/image.bbappend: not a BitBake file When I build image the packages in image.bb and all image.bbappend are present When I

问题 I want to include https://pypi.python.org/pypi/ndeflib in my image. Thus I created a recipe for this. Following are the contents of python-ndeflib_0.2.0.bb DESCRIPTION = "NFC Data Exchange Format decoder and encoder." SECTION = "devel/python" LICENSE = "CLOSED" SRC_URI = "https://pypi.python.org/packages/0c/0f/b9d94cee7847697469c49a25b4d23236de534451990b83008e6bf4fab15b/ndeflib-0.2.0.tar.gz" do_install_append() { rm -f ${D}${libdir}/python*/site-packages/site.py* } do_compile_prepend() { $

问题 UPDATE: bitbake core-image-minimal without any added layers gives me errors such as: ERROR: Task (/home/rama/repositories/oe-core/build/../layers/openembedded-core/meta/recipes-devtools/m4/m4-native_1.4.17.bb:do_compile) failed with exit code '1' I just initlized the repo like here https://developer.toradex.com/knowledge-base/board-support-package/openembedded-(core)#V21_and_Later_Images and made no changes whatsoever! Image 2.8 is giving me problems with a layers that requires things to be

问题 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 using yocto for creating initramfs and it creates initramfs and places the libraries in lib directory. I want to generate libraries for both 32 and 64 bit using yocto. In machine.conf I enabled MACHINE_FEATURES += "x86_64" How I generate binaries for both 32 and 64 bit using yocto in initramfs 回答1: You need to configure multilib build. Basically that boils down to something like this in your local.conf: MACHINE = "qemux86-64" require conf/multilib.conf MULTILIBS = "multilib:lib32"

问题 We have a single MACHINE which we use to build two target images; foo-image and foobar-image. Both images consume the same version of a package, but we would like to add a change to the do_install task based on which image is built. So that the recipe file for the package looks something like this: do_install (){ //Some work } do_install_append_foobar-image(){ //Some foobar work } Eventually when we do the build for the two images: MACHINE=custom bitbake foo-image MACHINE=custom bitbake

问题 I created a bitbake recipe for installing https://pypi.python.org/pypi/Adafruit-GPIO/1.0.3 python package. Following is my recipe DESCRIPTION = "Library to provide a cross-platform GPIO interface on the Raspberry Pi and Beaglebone Black using the RPi.GPIO and Adafruit_BBIO libraries" SECTION = "devel/python" LICENSE = "CLOSED" PR = "r1" SRC_URI = "https://pypi.python.org/packages/db/1c/2dc8a674514219f287fa344e44cadfd77b3e2878d6ff602a8c2149b50dd8/Adafruit_GPIO-1.0.3.tar.gz" inherit pypi

问题 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

问题 I'm trying to get /var/log to be persistent in my fido build. The default setting on poky is, that there is a symlink in /var which points log -> volatile/log . volatile is a mounted on a tmpfs. So far i figured out that the symlink should be created by the base-files recipe: volatiles = "log tmp" do_install () { ... for d in ${volatiles}; do ln -sf volatile/$d ${D}${localstatedir}/$d done ... I appended the base-files recipe so the link was not created, but it still turned up in my rootfs.

问题 I want copy folders and it's content to yocto during image build process. For this process I am using following recipe SUMMARY = "Installation Recipe" DESCRIPTION = "It installs folder" HOMEPAGE = "" LICENSE = "CLOSED" MY_FILES1 = "/home/jane/d1fold" MY_FILES2 = "/home/jane/d2fold" inherit allarch do_install() { install -d ${D}/home/root cp -R ${MY_FILES1}/* ${D}/home/root cp -R ${MY_FILES2} ${D}/home/root } FILES_${PN} += " /home/root" But I receive following error ERROR: QA Issue: weaved: