openembedded

How to make /var/log persistent in Yocto Fido (poky)

半城伤御伤魂 提交于 2019-12-10 04:29:17
问题 I'm trying to get /var/log to be persistent in my fido build. The default setting on poky is, that there is a symlink in /var which points log -> volatile/log . volatile is a mounted on a tmpfs. So far i figured out that the symlink should be created by the base-files recipe: volatiles = "log tmp" do_install () { ... for d in ${volatiles}; do ln -sf volatile/$d ${D}${localstatedir}/$d done ... I appended the base-files recipe so the link was not created, but it still turned up in my rootfs.

Unable to run Snappy player on Beaglebone Black using Yocto Project

隐身守侯 提交于 2019-12-08 12:47:38
My main objective is to run snappy player ( https://wiki.gnome.org/Snappy ) on target machine ( BeagleBone Black ) so, I wrote a recipe for Snappy player( snappy_1.0.bb ) as below LICENSE = "GPLv2" LIC_FILES_CHKSUM = "file://COPYING;md5=686e6cb566fd6382c9fcc7a557bf4544" SRCREV = "e73fabce4c397b40d490c74f6a6a0de000804f42" SRC_URI = "git://git.gnome.org/snappy" S = "${WORKDIR}/git" RDEPENDS_${PN} = "gtk+3 gstreamer1.0 glib-2.0 clutter-1.0 gstreamer1.0-plugins-base libxtst clutter-gst-3.0 clutter-gtk-1.0 libx11 cairo gdk-pixbuf" # inherit line inherit pkgconfig autotools FILES_${PN} += "${datadir

Unable to run Snappy player on Beaglebone Black using Yocto Project

99封情书 提交于 2019-12-08 04:32:10
问题 My main objective is to run snappy player (https://wiki.gnome.org/Snappy) on target machine ( BeagleBone Black ) so, I wrote a recipe for Snappy player( snappy_1.0.bb ) as below LICENSE = "GPLv2" LIC_FILES_CHKSUM = "file://COPYING;md5=686e6cb566fd6382c9fcc7a557bf4544" SRCREV = "e73fabce4c397b40d490c74f6a6a0de000804f42" SRC_URI = "git://git.gnome.org/snappy" S = "${WORKDIR}/git" RDEPENDS_${PN} = "gtk+3 gstreamer1.0 glib-2.0 clutter-1.0 gstreamer1.0-plugins-base libxtst clutter-gst-3.0 clutter

How to write own package for recipe in arago project build

試著忘記壹切 提交于 2019-12-07 22:15:41
问题 How can i write own package for recipe in arago project build? I know little bit that it can be bitbake files. But how can i write, no idea. I searched on internet, but failed to find any good source to start. can someone provide me link or example to start? Regards Linux Learner. 回答1: Create own recipe with Yocto using Bitbake: Use Yocto Project for Embedded systems. It's documentation and support is awesome. You can get started Yocto Project. Build your own recipe(for the first time build

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

和自甴很熟 提交于 2019-12-07 16:12:17
问题 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=$

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

一曲冷凌霜 提交于 2019-12-06 22:27:31
问题 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. 回答1: 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

How to write own package for recipe in arago project build

半世苍凉 提交于 2019-12-06 12:45:51
How can i write own package for recipe in arago project build? I know little bit that it can be bitbake files. But how can i write, no idea. I searched on internet, but failed to find any good source to start. can someone provide me link or example to start? Regards Linux Learner. Create own recipe with Yocto using Bitbake: Use Yocto Project for Embedded systems. It's documentation and support is awesome. You can get started Yocto Project . Build your own recipe(for the first time build takes quiet good amount of time) Getting Yocto Project: Follow step-by-step procedure given Gumstix

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} \ -

Can't boot basic OpenEmbedded-Core on Freescale i.MX28

折月煮酒 提交于 2019-12-05 23:34:12
问题 I've been trying to build and boot OpenEmbedded-Core on the evaluation kit for Freescale's ARM i.MX28, using the Freescale ARM layer for OpenEmbedded-Core. Unfortunately, I can't find a basic "Getting Started" guide (though there is a Yocto getting-started guide). Unfortunately, I haven't been able to "get started", to the point of successfully booting to a basic command prompt on the board's debug serial port. Here is what I've been able to piece together, and as far as I've managed to get