You can't patch a recipe depending on whether another recipe is going to be built, because the process is that recipes produce packages, and packages built images. So you're building two images, one

You can easily add .inc file which will set all the PREFERRED_VERSIONs for all components you need and then the users will just add an "require" of this .inc files to their

I am currently creating a new layer (which will eventually be made generally available). I need to provide both a versioned recipe, and an "unstable" one. Currently I have somepackage_1.0.bb and

Hi all. I need to check a small diversion on qt5-qtdeclarative package. I disable SSE2 check feature for qv8engine. There  is a way to execute a massive test of all QtQuick QML features over

Hi, I need to patch my custom recipe, let say "Package-A.bb" in which I need to add a patch to the test recipe if the yocto build has a specific package like let's say if "Package-B" is available

The Yocto Project Summit 2019 is quickly approaching and, with that, the CFP closing date. Quick reminder for everyone that plans to submit an abstract: CFP Closes: 11:59 PM PST on Monday,

colleague just asked how to generate an SPDX license "notice file" (whatever that is) from a build for a zynq ultrascale+ board, which shouldn't be hard other than that: 1) it's not pure YP, it's

I don't have tune2fs on my embedded system, so I can't check, but that sounds like the probable reason. The nanoseconds that ext4 added are in the upper 128 bytes of a 256 byte inode, for

SDKIMAGE_FEATURES ??= "dev-pkgs dbg-pkgs src-pkgs ${@bb.utils.contains('DISTRO_FEATURES', 'api-documentation', 'doc-pkgs', '', d)}" SDKs by default contain debug symbols, and yes they can be used

Hi, I'm not entirely sure if this is bug or feature. I've created sdk to my image with populate_sdk - command. I noticed that in the SDK the x86_64 - directory is 384MB and that contains all the

I ran into something similar in a Makefile. There the problem was that the default sub shell used is /bin/sh and does not support the "source" command. Solution for the Makefile I used is

Disable golang bindings to avoid potential host contamination issue. Fixes: https://bugzilla.yoctoproject.org/show_bug.cgi?id=13166 Signed-off-by: Yi Zhao <yi.zhao@...> ---

I think file timestamp resolution on ext4 is one of the things that depend on inode size (ext4 does not enforce reasonable values because of compatibility with earlier versions I guess). So maybe

<GWilson@...> wrote: My immediate thought was add: PREMIRRORS = "" to your ostree recipe - there's an old copy of the source sitting in the yocto mirrors and the gitsm fetcher doesn't

I'm trying to include ostree into a raspberry pi boot2qt build based on thud. I'm getting a warning: WARNING: linux-raspberrypi-1_4.14.112+gitAUTOINC+6b5c4a2508-r0 do_kernel_metadata: defconfig

Try asking NXP directly. Ross

Hi, Is there any way by which I can use the source command inside a bitbake recipe for example if I need to source some environment file before compiling. source <filename> doesn't seem to work Will

Hi I was trying to compile the rpmsg-lite library provided by NXP for my ZC102 board. While compiling I was getting the error as follows: | Scanning dependencies of target rpmsg-lite | [ 10%]

[Re: [meta-selinux][PATCH] conf/layer.conf: use BBFILES_DYNAMIC for dynamic layers] On 19.09.11 (Wed 09:22) Yi Zhao wrote: Okay, thanks. Funny that I randomly picked the package that was broken in

Hi all. I nee to disable all SIMD mmx sse extensions for the  GCC use to build the final image, containing Qt5 libraries Now I have  tuned qtbase_git.bb by PACKAGECONFIG_CONFARGS adding the