Hi Alexandre, Good Morning! I am not introducing any change to kernel. This is one of my project requirement to enable coverage support to kernel for specific build for my project. In my

Hi Alexandre, I am not pushing any changes to open source kernel. I want to enable few driver module in the kernel. That configuration want to have in file/ folder. My changes. Kern

On Tue, Jul 12, 2022 at 11:19 PM Bruce Ashfield via lists.yoctoproject.org <bruce.ashfield=gmail.com@...> wrote: As you can see, patches are on the list. This one was an awk

From: Bruce Ashfield <bruce.ashfield@...> Integrating the following commit(s) to linux-yocto/5.15: 6c085baf1838 tools: use basename to identify file in gen-mach-types Signed-off-by: Bruce

From: Bruce Ashfield <bruce.ashfield@...> Integrating the following commit(s) to linux-yocto/5.10: 80f5207b5abd tools: use basename to identify file in gen-mach-types Signed-off-by: Bruce

this is nice. I mistook it for the dependencies

That *will* be built, no. PACKAGES contains the packages which *can* be built, but also the do_package can create more. For example, it’s possible for a package which builds 20 plugins to

Bitbake -g recipe Might emit what you want in some form On Wed, Jul 13, 2022 at 2:40 PM simonblack.it via lists.yoctoproject.org <simonblack.it=yahoo.com@...> wrote:

Hi, Does yocto store all packages name that will be built from a recipe in a variable? BR, Simon

Thanks Martin and Mike for your explanations and tips. So, I've done a lot of testing today and it seems I simplified the example in my first email a bit too much. The example as-is works fine when

I wrote a similar thing a while back, to review the license checksums in a layer. It’s only in my ross/mut branch on poky-contrib right

"t-maiaxiao" <t-maiaxiao@...> writes: I've been working on meta-binaryaudit integration into CI in the Oniro Project [1]. We had to fork the project due to maintainer

<richard.purdie@...> wrote: Yet another generation script referencing itself .. they seem to like doing that. I don't get the warning, but I do have the file with the reference in it

Hello everyone, Microsoft is going to pick this up (the ABI compliance layer[0]) as an intern project again this summer, with a particular focus on improving code quality. I’ll be working on it for

Thanks, this test build showed two warnings. I have no idea why this only showed up now: beaglebone: WARNING: linux-yocto-5.15.52+gitAUTOINC+f122fe59e7_3ec00e9ee0-r0 do_package_qa: QA Issue: File

Thank you Nicolas for asking this question since I will probably run into this issue soon if not for this email thread. The answers so far have been very helpful but I just want to clarify a bit more

Quick answer: Don't build multiple distros in one build directory. You might get away with setting TMPDIR = "tmp-${DISTRO}" to give each its own. But I'd rather advice to set up two separate builds

Hi Nicolas, I stumbled over this issue as well. Think of it this way, the package gets built in one environment and then it's built. Now ask to build it in another environment -- but it's built

I'd suggest adding some "bogus" things to your machine-extra.conf, because I don't think the file will actually be used (or even parsed) anywhere. You can override SERIAL_CONSOLES in your DISTRO

From: Bruce Ashfield <bruce.ashfield@...> Updating linux-yocto/5.15 to the latest korg -stable release that comprises the following commits: 545aecd22961 Linux 5.15.52 ea512d540a55