yocto

How patching works in yocto

[亡魂溺海] 提交于 2019-12-06 07:18:33
I am using BBB to understand the yocto-project. I am not sure how patching works. This is my project directory ├── meta-testlayer ├── poky meta-test layer contains a helloworld example ├── conf │ └── layer.conf ├── COPYING.MIT ├── README └── recipes-hello └── helloworld ├── helloworld-0.1 │ ├── helloworld.c │ ├── helloworld.patch │ └── newhelloworld.c └── helloworld_0.1.bb helloworld.c and newhelloworld.c differ by only one printf statement. Here is the content of helloworld.c #include <stdio.h> int main(int argc, char **argv) { printf("Hi, this is my first custom recipe. Have a good day\n");

Yocto build for preempt_rt

眉间皱痕 提交于 2019-12-06 05:54:30
问题 I'm building a custom kernel for the beaglebone black. Following this guide (http://android.serverbox.ch/?p=1273) I'm able to boot to console successfully using a base image. When I try to build with the realtime kernel patch using command: bitbake core-image-rt I get the following error messages: Loading cache: 100% |###############################| ETA: 00:00:00 Loaded 1222 entries from dependency cache. Parsing recipes: 100% |#############################| Time: 00:00:00 Parsing of 862 .bb

Yocto: : does bitbake cleanall ,cleans dependencies as well

匆匆过客 提交于 2019-12-06 04:48:26
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 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 cleanall task it does not work. Removes all output files, shared state (sstate) cache, and downloaded source

IMX6Q学习笔记——开发板的Linux系统更新和烧录

試著忘記壹切 提交于 2019-12-06 02:09:26
IMX6Q学习笔记——开发板的Linux系统更新和烧录 记录自己在电鱼电子开发SAIL-IMX6Q全能板后,并且对系统和模块进行简单测试的过程之后对开发板的Linux系统进行更新和烧录的记录过程,算是进行一个分享和记录,同时也方便自己日后查阅。 首先准备好需要的硬件和软件。PC机(需要至少一路232串口和一路USB2.0 HOST)、串口线、USB转串口线、电源适配器、USB延长线。软件需要准备超级终端、mfgtools.rar、u-boot1.imx,u-boot2.imx,zlmage,sail-imxq.dtb,rootfs.tar.bz2。 使用PC机USB OTG连接SAIL-IMX6Q/DL的OTG接口。将12V直流电源连接到SAILIMX6Q/DL主板的电源接口。 设置USB烧写模式,码开关SW4拨到 1 0 。 从光盘\Linux\烧录映像目录下拷贝sail-imx6q.dtb到mfgtools\Profiles\Linux\OS Firmware\files\sail-imx6q文件夹中 从光盘\Linux\烧录映像目录下拷贝zImage到mfgtools\Profiles\Linux\OS Firmware\files\sail-imx6q文件夹中 从光盘\Linux\烧录映像目录下拷贝u-boot1.imx或u-boot2.imx到mfgtools

Ship extra files in kernel module recipe

无人久伴 提交于 2019-12-06 01:39:29
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/directories were installed but not shipped in any package: /usr /usr/bin /usr/bin/my_program Please set FILES

How can I change the installation path of an autotools-based Bitbake recipe?

风流意气都作罢 提交于 2019-12-06 00:15:16
I have an autotools-based BitBake recipe which I would like to have binaries installed in /usr/local/bin and libraries installed in /usr/local/lib (instead of /usr/bin and /usr/lib , which are the default target directories). Here's a part of the autotools.bbclass file which I found important. CONFIGUREOPTS = " --build=${BUILD_SYS} \ --host=${HOST_SYS} \ --target=${TARGET_SYS} \ --prefix=${prefix} \ --exec_prefix=${exec_prefix} \ --bindir=${bindir} \ --sbindir=${sbindir} \ --libexecdir=${libexecdir} \ --datadir=${datadir} \ --sysconfdir=${sysconfdir} \ --sharedstatedir=${sharedstatedir} \ -

During SDK build: environment-setup.d/ conflicts between attempted installs

限于喜欢 提交于 2019-12-05 15:41:34
I am trying to build an image for beaglebone that contains Qt5, as well as generate the SDK for this image. Problem my problem is, that the build fails the do_populate_sdk task to create the SDK with the following error: Error: Transaction check error: file /opt/poky/2.3.1/sysroots/x86_64-pokysdk-linux/environment-setup.d conflicts between attempted installs of nativesdk-cmake-3.7.2-r0.x86_64_nativesdk and nativesdk-qtbase-tools-5.8.0+git0+49dc9aa409-r0.x86_64_nativesdk A little further up the stream I encountered the following error message: ERROR: Could not invoke dnf. Command '/home/ubuntu

How to build Qt (with QtWebEngine support) using meta-toolchain-qt5?

拜拜、爱过 提交于 2019-12-05 15:26:29
I am trying to build Qt using meta-toolchain-qt5 , but when I do this via poky-glibc-x86_64-meta-toolchain-qt5-cortexa7hf-vfp-vfpv4-neon-toolchain-2.0.1.s‌​‌​h , I don't see anything about QtWebEngine in the sysroot directory. I also tried to build Qt using the following command bitbake meta-toolchain-qt5 but it is the same result; I don't have anything regarding Qt WebEngine. How can I build Qt with QtWebEngine support? Looking at meta-toolchain-qt5 it inherits populate_sdk_qt5 , which in turns adds packagegroup-qt5-toolchain-target to the SDK. Taking a closer look at packagegroup-qt5

Project ERROR: Unknown module(s) in QT: webengine

北战南征 提交于 2019-12-05 14:31:03
I have compiled a framebuffer (without x11 and wayland) image for wandboard-quad with Yocto Jethro. I have used the Freescale Community BSP Jethro branch.The image contains most of the Qt 5.5 components and Qt Web Engine. The qmake version is 5.5.1 from meta-toolchain-qt5 and Qt Creator is 5.5 as well. I created the quick nano browser example to test the functionalities. But, Qt Creator gives me this Project ERROR: Unknown module(s) in QT: webengine when I cross compile to wandboard. Desktop compile is fine though. Anyone knows what is wrong? Edit : I have follow how to set up Qt Creator in

Best practice for building firmware using Yocto

大城市里の小女人 提交于 2019-12-05 12:34:56
I have a working Yocto build system based on the rocko branch that is generating images for an ARM-based target board. One of the chips on this board is a small ARM-based micro-controller that is separate to the main CPU. It needs to be loaded with a firmware image that I have to build. It would be easy to make a recipe to build this microcontroller firmware. It requires an ARM cross compiler and then some special compiler options to control the code generation (for cortex-m4 + thumb etc). The trouble is, if I setup a normal recipe, it will assume that I'm building something for the target ARM