bitbake

How to setup an Yocto recipe to build from a local git source?

邮差的信 提交于 2019-12-04 08:52:19
Hej I am playing a bit around with Yocto, a Raspberry Pi and some code I wrote. Now I want that Yocto is building an image including the program I wrote. I like to know how to setup the fetcher to fetch from a local git repro. My setup is simple. The code is in the directory: /home/user/git/myTest I linked the directory into my recipe directory of my Yocto meta-layer. /home/user/poky/meta-test/myApp/myTest Because it is a local git repro, there is the ".git" folder. /home/user/git/myTest/.git There are more files: /home/user/git/myTest/CMakeLists.txt /home/user/git/myTest/src/main.cpp /home

bitbake SRC_URI file://

爷,独闯天下 提交于 2019-12-04 01:31:44
If I have a tarball, helloworld.tar.gz in a local directory, say /home/user/tarballs/, how can I make my bitbake recipe fetch from that directory? my helloworld.bb is SECTION = "examples" LICENSE = "Proprietary" LIC_FILES_CHKSUM = "file://COPYING; md5=1b1b8016e15e07a2fec59623ebf12345" SRC_URI = "file://helloworld.tar.gz" but when I bitbake, I get the below warning message: WARNING: Unable to get checksum for helloworld SRC_URI entry helloworld.tar.gz: file could not be found I read something about FILES and FILESEXTRAPATHS can influence the download path but not sure where/how to set them. I

Bitbake not installing my file in the rootfs image

让人想犯罪 __ 提交于 2019-12-03 19:13:10
问题 I have created a bitbake recipe that would copy 2 of my files (firmware binaries for VPU) into /lib/firmware/ directory on targets root filesystem. I have tried many options so I'm now not sure what in my recipe is unnecessary/redundant and what is needed. I think that FILESEXTRAPATHS.., SRC_URI.. and do_install.. should be enough but it doesn't work with just it and neither with all other stuff. DESCRIPTION = "VPU libraries provided by fsl" LICENSE = "MIT" LIC_FILES_CHKSUM = "file://$

Cmake with bitbake recipe

♀尐吖头ヾ 提交于 2019-12-03 17:45:47
问题 I am trying to build an yocto image with my own package. I have OpenCV code on github which uses cmake. I trying to write a recipe for it and facing lot of errors. Can any one give some hints on what functions or parameters to include in my recipe. My recipe looks as following DESCRIPTION = "cameracapture application" SECTION = "examples" LICENSE = "CLOSED" PR = "r0" DEPENDS += "opencv" SRC_URI = "git://https://github.com/zafrullahsyed/cameracapture.git;protocol=https;tag=v0.1" EXTRA_OECMAKE=

Machine specific layers in yocto

流过昼夜 提交于 2019-12-03 16:36:35
I want to add some layers fetch from upstream for a new machine (call it A) mainly just to use the machine A configure file, kernel and u-boot provided from those layers. However, the new layers have several bbappend files (with bb files as well) that the version is different with other machines' layers in my yocto project. For example, machine A has its own gstreamer1.0_1.8.1.bb and bbappend file. Other machines are using gstreamer1.0_1.6.1.bb . What happens when I build the image for the other machine is that it builds the version 1.8.1 because Yocto will always look for the newest

Is there a way to check the exact list of packages that will be installed in the image in Yocto?

混江龙づ霸主 提交于 2019-12-03 12:47:06
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. Yes, like this On old Bitbake versions: bitbake -g <image> && cat pn-depends.dot | grep -v -e '-native' \ | grep -v digraph | grep -v -e '-image' | awk '{print $1}' | sort | uniq Taken from the NXP Community website On

How to find which Yocto Project recipe populates a particular file on an image root filesystem

时光总嘲笑我的痴心妄想 提交于 2019-12-03 12:21:31
问题 I work with the Yocto Project quite a bit and a common challenge is determining why (or from what recipe) a file has been included on the rootfs. This is something that can hopefully be derived from the build system's environment, log & meta data. Ideally, a set of commands would allow linking a file back to a source (ie. recipe). My usual strategy is to perform searches on the meta data (e.g. grep -R filename ../layers/* ) and searches on the internet of said filenames to find clues of

Bitbake recipe not applying patch as expected

余生颓废 提交于 2019-12-03 11:17:10
问题 I have a tarball src.tar.gz whose contents are unpacked into src/ and a patch of this sources generated with this command: $ diff -Nurp src/ src_mod/ > my.patch The patch header starts with this three lines: diff -Nurp src/path/to/file src_PATCHED/path/to/file --- src/path/to/file 2012-10-22 05:52:59.000000000 +0200 +++ src_PATCHED/path/to/file 2016-03-14 12:27:52.892802283 +0100 My bitbake recipe references both path and tarball files using this SRC_URI: SRC_URI = " \ file://my.patch \ file:

Bitbake runtime vs build dependency

允我心安 提交于 2019-12-03 11:02:23
问题 I am having trouble understanding the bitbake recipes. (I have some poorly written I need to modify, I usually would read and understand the whole mechanism but sadly I am on a tight schedule). Can you please help me understand the difference between RDEPENDS and DEPENDS. I read the reference and I know that they stand for runtime dependency and build dependency respectively, but what is the effect on it in a bitbake recipe? As far as I understand, if a package A depends on another B, B has

do_install error while running custom bitbake in poky build

感情迁移 提交于 2019-12-03 08:50:17
I am using latest poky-am335x to build simple helloworld application. With some workaround I can able to compile the application. I am doing lot of trails to install binaries but build is throwing error. error log : DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common'] DEBUG: Executing shell function do_install NOTE: make -j 4 DESTDIR=/home/pis1kor/workspace/poky-am335x/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/helloworld-1.0-r0/image install make: *** No rule to make target `install'. Stop. ERROR: oe