yocto

I am creating an image containing standard recipes and my owns. I wanted to list the licenses I use in all of the included packages and later check if I can use them for commercial application for example. I had the bad surprise packagegroups have a LICENSE flag already. I noticed it doing: bitbake -e -n -v core-image-minimal | grep "LICENSE" It returns LICENSE=MIT since it is defined in the bb file. But I have no information about all the included packages. This MIT has been put manually in the core-image-minimal.bb, but I'd be interested in all dependencies. I have the same issue for my .bb

I would like to install/copy all my directories and files recursively from working directory to my target package rootfs on yocto build system. I tried the solution provided by Tobias Bystricky in How to install directory structure recursively in OpenEmbedded BitBake recipe? but I faced "No such file or directory" error I did , install -d ${D}${sysconfdir}/xxx/ install -d ${D}${sysconfdir}/xxx/yyy install -d ${D}${sysconfdir}/xxx/yyy/zzz install -d ${D}${sysconfdir}/xxx/yyy/zzz/kkk find ${WORKDIR}/xxx/yyy/zzz/kkk/ -type f -exec 'install -m 0755 "{}" ${D}${sysconfdir}/xxx/yyy/zzz/kkk/' \; Error

I've got a couple of HW platforms (same cpu, etc.) that require different asound.conf files. The way that I'm controlling the target platform is via the MACHINE variable and target image (i.e., MACHINE=machine_1 nice bitbake machine-1-bringup-image ) Normally, if just replacing the conf file I'd just create an alsa-state.bbappend and create a do_install_append function to replace it. However since the different HW platforms require differ conf files I'm unsure how to handle it. I've tried putting some logic into the append file do_install_append function but it's not working out. It's not

Recently I just used fsl-community-bsp and meta-qt5 layer to generate the cross toolchain and the rootfs. I used "bitbake meta-toolchain-qt5" and "bitbake fsl-image-multimedia-full". Both fsl-community-bsp and meta-qt5 use jethro branch. Following are some of my questions: In the rootfs which I put in the “riotboard”, is qt5 library already in it? Do I need to compile the source of qt5 and copy it to the board separately?--- Now it's clear, the library are inside the rootfs; I have set up the qtcreator: device, kit, qt version, compiler, debugger, also ssh connection, but when I run the

https://www.yoctoproject.org Yocto offical web System envn. Git 1.8.3.1 or greater tar 1.27 or greater Python 3.4.0 or greater. sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \ build-essential chrpath socat cpio python python3 python3-pip python3-pexpect \ xz-utils debianutils iputils-ping python3-git python3-jinja2 libegl1-mesa libsdl1.2-dev \ xterm The first demo. download poky-sumo-19.0.3.tar.bz2 from web and extract it. The default machine is x86. The first thing is to init the env. by run below script source oe-init-build-env command to build: bitbake core

My images, built with bitbake , must contain different packages for different machines (say, I need to add package package1 to image for machine1 , but not for machine2 ). It is possible to add line IMAGE_INSTALL_append_machine1 = " package1" to the image recipe. But I do not think this is sustainable, as IMAGE_INSTALL_append_machine1 may be defined in some other recipe (which is not under my control) and the earlier definition gets overwritten with the later one. This is what I think Yocto Project Development manual warns about using IMAGE_INSTALL . Is my concern valid? What is the proper way

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 achieve using service_0.1.bb # This recipe performs the following tasks # 1) Install .sh file in /home