<richard.purdie@...> wrote: Faster builds in the common cases seems like a great idea! If someone really needs the old behavior, is there a mechanism to do the equivalent to what it

wrote: This change is probably high impact in that it changes behaviour the most of any of the changes. It does make image builds use a lot less sstate and in theory, if there are issues with failures

wrote: I've marked this one as an RFC since it caused a fair bit of pain even in OE- core due to recipes having pkgconfig class inherits missing. We do really want to do this and correctly mark up

There are several dependencies which recipes have which are not needed at runtime, only at build time. Extend the list of these from bison to include quilt, patch, meson, autoconf, automake and ninja

This class was added by me back in 2007 and has changed one for a whitespace issue since. It only has two lines and neither are particularly useful, one was replaced by the nopackages class, the other

The class adds an emtpy PACKAGES setting but most code now uses the nopackages class which is much clearer. It also adds recursive do_build dependencies which don't really serve any useful purpose any

The 'meta' is old and not very useful. It empties PACKAGES and creates recursive do_build dependencies. We shouldn't need such recursive build dependencies any more so simplify the code. This does

This is a controversial change which removes the recursive dependencies from the do_build target of packaging tasks of recipes. Currently this means when you "bitbake <image>" or "bitbake

This sstate task is only needed when depended upon, it can be skipped if there are no tasks running that directly depend upon it. This reduced the number of sstate tasks in something like an

If an image is built from sstate, the cross toolchain was being pulled in. This was due to the sstate dependencies for deploy tasks not being considered in the "depvalid" logic. do_deploy tasks do

Deploy is a tricky task as it isn't in SSTATETASKS as it isn't always present. We do need to ensure dependency chains around do_deploy tasks are correctly handled as sstate tasks though. For now add

The populate_sysroot task isn't enough for qemu-helper-native, we need it's addto_recipe_sysroot task. This corrects what amounts to bad dependency information to be explicit. Signed-off-by: Richard

This was being provided by other pieces of the dependency chain but is specifically required by configure and could fail if those pieces come from sstate. Fix such builds by adding the missing

Various recipes were missing a pkgconfig inherit or pkgconfig-native dependency despite using pkgconfig. Add the inherit to

Issue is in an experimental extension we don't have/use. Could also be windows only. Signed-off-by: Richard Purdie <richard.purdie@...> ---

Includes a fix for CVE-2021-40528. Signed-off-by: Richard Purdie <richard.purdie@...> --- .../libgcrypt/{libgcrypt_1.9.3.bb => libgcrypt_1.9.4.bb} | 2 +- 1 file changed, 1

Signed-off-by: Richard Purdie <richard.purdie@...> --- ...1e135a16091c93f6f5f7525a5c58fb7ca9f9.patch | 207 ++++++++++++++++++ meta/recipes-support/vim/vim.inc | 2 + 2

Distros need to switch to use SDKPATHINSTALL.  This change breaks the poky default value instead of any distro that has customised and disables the SDK hard coded path fix which was the original

Previously the SDKPATH can be used to custumize the path of the SDK installation. Drop the SDKPATH and use SDKPATHINSTALL without that brokes backwards compatible for any distro with SDKPATH