yocto

问题 Hi this is my layer tree ├── conf │ └── layer.conf ├── COPYING.MIT ├── README └── recipes-hello ├── helloworld │ ├── helloworld-0.1 │ │ ├── helloworld.c │ │ ├── helloworld.patch │ │ └── newhelloworld.c │ └── helloworld_0.1.bb ├── message │ ├── message-0.1 │ │ └── message.txt │ └── message_0.1.bb └── service ├── service-0.1 │ ├── test_systemd.service │ └── test_systemd.sh └── service_0.1.bb Here test_systemd.service is the service file which have to invoke test_systemd.sh, which I am trying to

问题 I'm new to Yocto Project. The initial idea is to create a custom image based on core-image-full-cmdline (this is with no windowing system) and generate a Qt5 SDK against this image. So my target to be able to run Qt applications needs to have some headers & libraries installed, isn't ? What I must specify on my image recipe ? Doing $ bitbake my_image -c populate_sdk will generate my_image with Qt5 support + SDK installer ? As I understood, to get a Qt SDK the steps would be: Download and add

问题 In Yocto-based Embedded Linux distributions, I am really interested in finding the complete list of packages/recipes/kernel modules from each dependent layers that will be built and installed to an image file before executing the image building recipe such as: bitbake my-image-minimal Is there a way to achieve this? Any guidance in this regard is appreciated. Thanks in advance. 回答1: Yes, like this On old Bitbake versions: bitbake -g <image> && cat pn-depends.dot | grep -v -e '-native' \ |

问题 More and more Linux distributions use python 3.x as default python, but Yocto still uses python 2.7. How to use Yocto with one of those distributions? 回答1: Yocto always runs in a virtualenv. But I've found a way to trick it to use python 3 : $ source oe-init-build-env build $ mkdir build/python-bin $ ln -s /usr/bin/python2 build/python-bin/python $ ln -s /usr/bin/python2-config build/python-bin/python-config $ export PATH=$(pwd)/build/python-bin:${PATH} Thanks all for your help ! 回答2: The

问题 How to generate an image with Sato and Chromium for the DragonBoard 410c? Starting from the qcom-oe-manifest referred in the Dragonboard-410c-OpenEmbedded-and-Yocto documentation What is the correct/proper way to add Sato desktop and Chromium to this base config? What's I have done: Added x11-base x11-sato to IMAGE_FEATURES Added chromium alsa-utils lsb to CORE_IMAGE_BASE_INSTALL my-image.bb /oe-qcom-yocto/sources$ more ./meta-rpb/recipes-samples/images/my-image.bb SUMMARY = "Basic console

问题 I need to start my own systemd service, let's call it custom.service . I know how to write a recipe for it to be added and enabled on boot: SYSTEMD_SERVICE_${PN} = "custom.service" SYSTEMD_AUTO_ENABLE_${PN} = "enable" However, it conflicts with one of the default systemd services - systemd-timesyncd.service . Is there a nice preferred way to disable that default systemd service in my bitbake file even though the systemd_XX.bb actually enables it? I can create a systemd_%.bbappend file to

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

问题 I have a Yocto BSP with my own layer that includes an autotools 3rdy part library (libcoap). My application ".bb" file has the following lines, telling libcoap is needed: DEPENDS += "libcoap" RDEPENDDS_${PN} += " libcoap libcoap-dev libcoap-devstatic" I can see the library files are being copied to sysroot: $ ls -l /projects/oe-core/build/tmp-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/coap-playground/1.0-r0/recipe-sysroot/usr/lib/libcoap* -rw-r--r-- 2 udev udev 286430 Ago 21 13:53

问题 I created a new layer over an existing Yocto git for my company project. In this layer I added a few external autotools based libraries. A few applications need to link against this libraries and the application projects are all cmake based. Taking one of this libraries (e.g. libcoap) I could easily find some FindCoAP.cmake to add to my library recipe. Now if I was running on PC, it would simply be a matter of placing this FindCoAP.cmake file in cmake 's ${CMAKE_ROOT}/Modules dir, but how

问题 I am using SAMA5D27-SOM-EK1 embedded board. I build for it Linux image OS using YOCTO project version SUMO. I need to know device's GPIOS ( gpios-leds and gpios keys specialy) and the mapping of the board. When I enter in /sys/firmware/devicetree/base/leds/red for example in the board terminal I can find gpio file but when i open it there are symbols which i can't read. I think that I can find such things in the generated Device Tree but i can't find its path! Please help me out 回答1: Here is