bitbake

I have a directory of 'binary' (i.e. not to be compiled) files and just want them to be installed onto my target root file system. I have looked at several articles, none of which seem to work for me. The desired functionality of this recipe is: myRecipe/myFiles/ --> myRootFs/dir/to/install My current attempt is: SRC_URI += "file://myDir" do_install() { install -d ${D}/path/to/dir/on/fs install -m ${WORKDIR}/myDir ${D}/path/to/dir/on/fs } I can't complain about the Yocto documentation overall, it's really good! Just can't find an example of something like this! You just have to copy these

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="" do_configure() { cmake ../ } inherit pkgconfig cmake I followed these tutorials to write my recipe

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 possible responsible recipes. However, this is not always very effective. In many cases, filenames are not

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://src.tar.gz \ " do_fetch and do_unpack tasks work as expected, leaving my.patch and src/ inside ${S}

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 to be built and ready to enable A to build. Bitbake isn't related to the runtime, it's only there for

I am attempting to write a recipe that would simple copy two files (MyfileA , MyfileB) to a specific directory when the overall image is built. This is what my directory structure looks like: MyDir/MyRecipe.bb MyDir/files/MyfileA MyDir/files/MyfileB I would like the two files to be copied to a folder in home (which would not exist initially hence the directories should be created)The folder lets say is called "Testfolder" This is what my bitbake file looks like DESCRIPTION = "Testing Bitbake file" PR = "r0" SRC_URI = "file://MyfileA \ file://MyfileB " do_install() { install -d MyfileA ~

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

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