bitbake

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

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

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

How to specify which kernel to build with bitbake/yocto

这一生的挚爱 提交于 2019-12-05 03:23:54
I am working on generating a new BSP using yocto daisy. When I build my image I get these warnings: NOTE: Resolving any missing task queue dependencies NOTE: multiple providers are available for virtual/kernel (my-kernel, linux-dummy) NOTE: consider defining a PREFERRED_PROVIDER entry to match virtual/kernel NOTE: multiple providers are available for runtime kernel-modules (my-kernel, linux-dummy) NOTE: consider defining a PREFERRED_PROVIDER entry to match kernel-modules I can't understand how to define my preferred provider for the kernel. From what I have read I should just need to add it to

How do I add more python modules to my yocto/openembedded project?

百般思念 提交于 2019-12-05 02:57:05
I wish to add more python modules to my yocto/openembedded project but I am unsure how to? I wish to add flask and its dependencies. some python packages having corresponding recipes in the meta folders, like Enum class for example: meta-openembedded/meta-python/recipes-devtools/python/python-enum34_1.1.6.bb unfortunately lot's of useful classes aren't available, but some might be needed for the python application. get used of installing missing packages using pip already on booted platform? but what if the target product is not IP network connected? the solution is to implement a new recipe

Machine specific layers in yocto

此生再无相见时 提交于 2019-12-05 02:00:11
问题 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

Unable to connect to bitbake server

陌路散爱 提交于 2019-12-04 15:32:53
Im trying to setup bitbake tool and trying to follow the tutorial https://www.yoctoproject.org/docs/1.8/bitbake-user-manual/bitbake-user-manual.html#bitbake-examples Now when I run the bitbake command I get the following error, p@p-ubuntu:~/ba/bitbake$ bitbake NOTE: Retrying server connection... (Traceback (most recent call last): File "/home/p/ba/bitbake/lib/bb/main.py", line 428, in setup_bitbake topdir, lock = lockBitbake() File "/home/p/ba/bitbake/lib/bb/main.py", line 480, in lockBitbake lockfile = topdir + "/bitbake.lock" TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'

How do I write a yocto/bitbake recipe to copy a directory to the targe root file system

ぐ巨炮叔叔 提交于 2019-12-04 11:13:08
问题 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