[yocto] Getting a recipe's files from within an image recipe

I have an app which has a config file, and I'd like my two images (production and dev) to have different configs. Obviously it'd be neater to keep the two config files within the recipe's directory structure. I guess I can't do this in the app's recipe since it has no concept of what image it

[yocto] PROVIDES problem building u-boot variants

Let's see if I can explain this well... I created a recipe to build a u-boot variant (for prod'n programming) - "u-boot-PLATFORM-mfg-sec.bb" - which has : require u-boot-PLATFORM.inc UBOOT_MACHINE = "tx6s-8035_mfg_sec_config" SRC_URI += "file://tx6s-8035_mfg_sec_defconfig" And 'bitbake

[yocto] Specifying MACHINE when setting up build environment

Is there a way to specify what MACHINE is put into local.conf when first setting up the build directory with oe-init-build-env? I have my own TEMPLATECONF which I use, but I'd like to be able to set the MACHINE on the command line rather than having to then modify local.conf --

[yocto] Using a poky recipe's files in a custom recipe

The current Poky I'm using (krogoth) has a recipe for dropbear, but I want to upgrade to use the latest version of dropbear. For source control reasons, I don't want to modify what's in meta/recipes-core/dropbear and therefore want to have my own recipe in my own layer. Yet for cleanliness I'd

[yocto] Slightly varying builds

I need to build two slightly varying versions of our Yocto build - one for the production units and one for development. They differ in only a few ways - the kernel and apps are the same. But one has Dropbear, whilst the other doesn't; and the U-Boot configs & patches are different. I'm

[yocto] Custom recipe - resolving "do_package_qa: QA Issue: -dev package contains non-symlink .so"

I have a custom recipe (for the AWS SDK), which is failing at the package_qa stage. The recipe is a very basic cmake styley, and on its own seems to begin with: 'bitbake -f -c package aws-sdk' completes without errors. But for 'bitbake -c package_qa aws-sdk) I get: ERROR: aws-sdk-1.1.31-r0

[yocto] Understanding dtb generation wrt uboot (with signing)

I'm working on 2.2/Morty, with a custom board. Ultimate goal is to create a FIT image with a signed configuration. But I'm trying to just work through step by step and understand the relationships between u-boot, kernel, dtb, and the fit image - would appreciate any guidance! So far, I've built

[yocto] Problems with 'configure' on own recipe [after moving to morty]

This is gonna be a bit of a hard one to describe concisely, but hoping someone can advise me on solving it I have a recipe of my own for an app (NetworkManager) which fetches the source from its git repo. This recipe works on krogoth, but is throwing up configure errors on morty. The recipe

[yocto] Migrating from krogoth to morty (can't boot fitImage)

I'm trying to migrate my krogoth environment to morty. I have custom recipes for u-boot and kernel; the only change necessary to build under morty was to patch u-boot for gcc6  - other than that the source versions and configs used are the same. On krogoth I can boot a fitImage kernel, but not on

[yocto] Getting linker -l into a bbappend

I have an autotools (C++) app which builds fine with my default recipe. But for a particular platform an additional (C) library is needed, so I have a bbappend. I can add in the additional compiler flag here, but I'm struggling to specify the additional library linkage - I think it's because the

[yocto] Configure errors in my recipe

I'm trying to put together a recipe for a package (NetworkManager-pptp), but hitting some peculiar errors in the configure. I'm building from tarball, and the recipe currently includes inherit autotools-brokensep gettext and DEPENDS = "intltool-native gettext-native" I'm not sure what it means

[yocto] Remove/prevent a package's installed files if another package present

I'd like to do a mod to my ppp recipe such that ip-up & ip-down aren't installed if another package is in the image recipe i.e. set in CORE_IMAGE_EXTRA_INSTALL. I guess I could do a do_install_append() or a pkg_postinst_(), but is there a way to detect the other package within the recipe? E.g.

[yocto] xsltproc failing to load docbook.xsl

I'm trying to build a package which uses xsltproc, and it's failing to load docbook.xsl: | /home/colin/100051/fsl-community-bsp/build/tmp/sysroots/x86_64-linux/usr/bin /xsltproc --output man/nmcli.1 --path man --xinclude --nonet --stringparam man.output.quietly 1 --stringparam funcsynopsis.style

[yocto] Missing dependencies on driver header

I have a niggly problem I keep running into, especially with fresh image builds. I have a custom driver, and a user-space library for controlling it; therefore the library includes one of the driver's header files (IOCTL defs etc). However I can't get the dependencies correct in the library

[yocto] gobject introspection needing pygobject (cross-compilation)

I've got a few packages in my image which need gobject introspection. (x86-64 host, ARM target) One is building fine, but the other - NetworkManager - is failing to generate the introspection data because it can't analyse the cross-compiled library. Apparently it uses pygobject in doing this, and

[yocto] Unpack hierarchy - jethro vs. krogoth

Is there a change to recipe parsing and/or variables between jethro and krogoth? I'm migrating from the former to the latter and have hit a patch failure. Looking at the unpacked source, jethro has the relevant file at build/tmp/work/XXX-poky-linux-gnueabi/linmux/3.0.2-r0/driver/ whereas

[yocto] Current situation with gobject introspection?

I'm currently using Jethro (though about to move to Krogoth), and have an external package which need gobject introspection. I'm building on 64-bit x86, for ARM iMX6 target. I've been searching around to work out if this is possible under Yocto, but not sure which of the info I've found is

[yocto] Out-of-tree module errors installing its udev rule

I've got a strange (to me) problem with the recipe for an out-of-tree kernel module. I'm trying to add a udev rule for the driver - in itself the recipe does the build ok, but building the full rootfs image throws up a "QA Issue: linmux: Files/directories were installed but not shipped in any

Re: [yocto] DEPENDS only half working

Fantastic - thanks. (Thought it must have been something simple!) -Original Message- From: Patrick Ohly [mailto:patrick.o...@intel.com] Sent: 01 February 2017 10:48 To: colin.helliw...@ln-systems.com Cc: yocto@yoctoproject.org Subject: Re: [yocto] DEPENDS only half working On Wed,

[yocto] DEPENDS only half working

I've got an odd problem with a pair of recipes: App 'bar' uses 'libfoo', so I've set a DEPENDS in bar.bb - I can see this is being half picked up, because 'bitbake bar' shows both builds being started. However bar isn't waiting on libfoo - bar tries to compile before libfoo has even finished

Re: [yocto] Making header of out-of-tree module available

Thanks Daniel, I’ve given that a try, but the header isn’t appearing (with ‘bitbake rfctrl’) anywhere but the module’s own workdir. It’s recipe is SUMMARY = " RF driver" LICENSE = "GPLv2" LIC_FILES_CHKSUM = "file://COPYING;md5=12f884d2ae1ff87c09e5b7ccc2c4ca7e" inherit module

[yocto] Making header of out-of-tree module available

I have a recipe which builds my own (out-of-tree) driver module - this packages/installs the module fine. (It's recipe has "inherit module"). Now I'm writing a recipe to build a library which uses the driver. What's needed to get the driver's header file 'exported' so that it can be included by

Re: [yocto] QEMU with host USB serial

Hi, That gives: Continuing with the following parameters: KERNEL: [/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/deploy/images/qemux86- 64/bzImage-qemux86-64.bin] ROOTFS: [/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/deploy/images/qemux86-

Re: [yocto] QEMU with host USB serial

'chown' that is, not 'chmod'! From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of colin.helliw...@ln-systems.com Sent: 26 January 2017 14:22 To: 'Yocto discussion list' Subject: [yocto] QEMU with host USB serial .. I've done a

[yocto] QEMU with host USB serial

I'm investigating using qemu to give us some test capability, for which we need to use the host's serial devices. I have a qemu build which boots up fine; I'm trying to give it access to the host USB. To keep it simple(r), I've seen mention of FTDI's device (0403:6001) in the qemu source so

Re: [yocto] Changing over to systemd (no dhcp)

Looking at it in more detail, it's perhaps more that not everything is taken up by systemd i.e. I have lots of symlinks to /dev/null in etc/systemd/system, with the corresponding/original SysV script still in /etc/init.d. Things like banner, sysfs, urandom, dmesg (to name just a few). Maybe

Re: [yocto] Changing over to systemd (no dhcp)

Thanks for all the pointers everyone. I've now got (in my distro conf): DISTRO_FEATURES_append = " systemd" DISTRO_FEATURES_remove = " sysvinit" VIRTUAL-RUNTIME_init_manager = "systemd" PREFERRED_PROVIDER_udev = "systemd" PACKAGECONFIG_append_pn-systemd = " resolved networkd" It's booting

Re: [yocto] Changing over to systemd (no dhcp)

Thanks Chen. Currently looking into getting networkd hooked in. (no luck yet!) I'll also look into moving stuff from local.conf to elsewhere, but where you say "Distro conf files are not suitable for such kinds of modification", I'm wondering what sort of modifications they *are*

Re: [yocto] Changing over to systemd (no dhcp)

Yes, I’d agree with that, Rick. We run automated regression builds from a fresh version control checkout – but because local.conf is generated when the build environment is set up, it isn’t suitable for version control. So any mods to it found during development have to be (remembered to be)

[yocto] Changing over to systemd (no dhcp)

We have a configuration for our embedded system which is working via SysV, but we're investigating moving over to systemd. Not sure if this is 'wise' - if anyone has technological arguments for/against then I'd be interested - but I wanted to investigate it anyway. I've modified local.conf

Re: [yocto] Adding to inittab based on image content

Thanks Rudi, that's got it. -Original Message- From: Rudolf J Streif [mailto:rudolf.str...@gmail.com] Sent: 06 January 2017 17:18 To: yocto@yoctoproject.org; colin.helliw...@ln-systems.com Subject: Re: [yocto] Adding to inittab based on image content Hi Colin, The correct way of doing

[yocto] Adding to inittab based on image content

Hi, I have a custom recipe for an application, and the app also needs an entry adding to inittab. I'd like to trigger this, obviously, only when the app is included in the image. I came across some hints at how to do this -

[yocto] Building a package for target and native

I'm creating a recipe for a 3rd party package. Part of its install is to create the target's config file by running *itself* - obviously this doesn't work as the target cpu is different to the host. I should be able to do a simple patch to alter the executable that the Makefile runs to generate

[yocto] Adding a file into the kernel source

I want to add a new file (a device tree source) into my kernel build. Is there a way to get the recipe to specifically copy an existing file in , or does it have to be created using a patch? -- ___ yocto mailing list yocto@yoctoproject.org