bitbake

问题 Do you got any idea how to build an oe project with distributed bitbake compile? I've thinked about distcc. export PATH=~/distcc/bin:$PATH make -jn CC=linux-gcc make will call linux-gcc from my path which points to distcc. distcc will schedule the tasks to all known hosts. -jn will create n6 instances of make. It works fine. But now I want to use distcc with bitbake. I know how to use -jn with bitbake. Just use export PARALLEL_MAKE=-jn But how to use export PATH=~/distcc/bin:$PATH with

问题 I am attempting to create a fairly simple BitBake recipe that uses autotools, which you can see here: SUMMARY = "an example autotools recipe" LICENSE = "MIT" LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302" inherit autotools SRC_URI = "file://${TOPDIR}/piu/geo_utilities" S = "${TOPDIR}/piu/geo_utilities" After starting a BitBake build with this recipe's default package included, do_configure fails with the following: configure: exit 0 WARNING: /home

问题 I'm facing something new in my experience. An updated Yocto environment fails to build while fetching MariaDB : WARNING: mariadb-5.5.64-r0 do_fetch: Failed to fetch URL https://downloads.mariadb.org/f/mariadb-5.5.64/source/mariadb-5.5.64.tar.gz, attempting MIRRORS if available ERROR: mariadb-5.5.64-r0 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-BIEhFRRkoA"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export

问题 I am working on the Dora branch (Poky 1.2) of Yocto and need to work on this branch only. I need to change the blank root password to some other value in order to prevent a security hole in the image during development. How do I set the root password? I would like to use the local.conf file. The method described here does not work: How to set root password on Yocto / Poky image? 回答1: Add the below line in your build/conf/local.conf or go to your meta-dir and add the below line for taking git

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

问题 I am trying to create a simple Yocto Python Recipe for Python 3 PyTorch. The target is an SD Card Image for the NVIDIA Jetson Nano produced by Yocto from the meta-tegra layer. I can successfully compile and boot an image from meta-tegra without these recipes. NVIDIA themselves have compiled and released the ".whl" Python packages and they are found here: https://devtalk.nvidia.com/default/topic/1048776/official-tensorflow-for-jetson-nano-/ Using their build instructions, I tried to write a

问题 bitbake cleanall Removes all output files, shared state cache, and downloaded source files for a target It is not clear or documented if it cleans all build time dependencies as well 回答1: Please read the mega-manual section do_cleanall . do_cleanall removes: all output files shared state (sstate) cache and downloaded source files for a target (i.e. the contents of DL_DIR). You can run this task using BitBake as follows: $ bitbake -c cleanall <recipe-name> If recipe name is not passed to

问题 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 am working on generating a new BSP using yocto daisy. When I build my image I get these warnings: NOTE: Resolving any missing task queue dependencies NOTE: multiple providers are available for virtual/kernel (my-kernel, linux-dummy) NOTE: consider defining a PREFERRED_PROVIDER entry to match virtual/kernel NOTE: multiple providers are available for runtime kernel-modules (my-kernel, linux-dummy) NOTE: consider defining a PREFERRED_PROVIDER entry to match kernel-modules I can't understand