Re: [OE-core] [PATCH] cmake.bbclass: Add ${COREBASE}/scripts to CMAKE_FIND_ROOT_PATH

2024-04-17 Thread Chuck Wolber
On Wed, Apr 17, 2024 at 12:14 Khem Raj via lists.openembedded.org wrote: > > > On Wed, Apr 17, 2024 at 4:25 AM Daniel Klauer via lists.openembedded.org > wrote: > >> ${COREBASE}/scripts contains a "git" wrapper disabling fakeroot/pseudo. >> This patch allows CMake to find

Re: [OE-core] [PATCH] mirrors: Switch llvm to use shallow cloning

2024-03-15 Thread Chuck Wolber
On Wed, Feb 28, 2024 at 2:39 PM Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > The llvm github repo appears to see a lot of churn on branches we're not > interested in and is in general huge and unreliable to clone. > > Switch to shallow clones to improve the user experience. >

Re: [OE-core] [PATCH v2] image-live: Add support for building EFI-bootable ISO images for non-x86-based archs

2023-11-28 Thread Chuck Wolber
On Tue, Nov 28, 2023 at 11:50 AM Ross Burton wrote: > On 28 Nov 2023, at 19:00, Chuck Wolber wrote: > > > > On Tue, Nov 28, 2023 at 9:55 AM Ross Burton wrote: > > > > I’ll reply with comments on the code shortly, but my initial thoughts > are mainly does anyone

Re: [OE-core] [PATCH v2] image-live: Add support for building EFI-bootable ISO images for non-x86-based archs

2023-11-28 Thread Chuck Wolber
On Tue, Nov 28, 2023 at 9:55 AM Ross Burton wrote: > > I’ll reply with comments on the code shortly, but my initial thoughts are > mainly does anyone actually use ISO images still, especially on non-x86 > systems? I’m curious what problem you’re trying to solve here. > I can only speak for the

Re: [OE-Core][RFC] update-layers: Update layers managed by setup-layers

2023-07-12 Thread Chuck Wolber
ts the above thinking. ..Ch:W.. On Wed, Jul 12, 2023 at 11:20 AM Alexander Kanavin wrote: > Thanks, perhaps this functionality should simply be folded directly > into bitbake-layers perhaps, as an extension of 'create-layers-setup'? > Does it need to be in a separate script? > > Alex &

[OE-Core][RFC] update-layers: Update layers managed by setup-layers

2023-07-12 Thread Chuck Wolber
I wrote this tool to do automatic updating of layers managed by the setup-layers script. This addresses some of the functionality I discussed in my OSSNA 2023 talk . A detailed explanation of what the following script does is found in the comments, but

Re: [OE-core] [PATCH v2] scripts/oe-setup-layers: Make efficiently idempotent

2023-01-17 Thread Chuck Wolber
On 1/17/23, 9:05 AM, "Alexander Kanavin" mailto:alex.kana...@gmail.com>> wrote: > On Tue, 17 Jan 2023 at 18:03, Luca Ceresoli via lists.openembedded.org > > wrote: > > > I'm afraind I am unable to apply this patch on my testing branch as it > >

[OE-core] [PATCH v2] scripts/oe-setup-layers: Make efficiently idempotent

2023-01-16 Thread Chuck Wolber
intent to use "bitbake-layers create-layers-setup destdir" to keep pace with upstream activity for those who wish to use it that way. Signed-off-by: Chuck Wolber --- scripts/oe-setup-layers | 55 + 1 file changed, 46 insertions(+), 9 del

Re: [OE-core] [PATCH] Make oe-setup-layers efficiently idempotent

2023-01-16 Thread Chuck Wolber
On 1/16/23, 9:00 AM, "Richard Purdie" mailto:richard.pur...@linuxfoundation.org>> wrote: %< SNIP %< > Making the script rerun successfully seems sensible so the change > itself is reasonable. I was a little confused by some of the comments > in the commit message as oe-setup-layers doesn't

[OE-core] [PATCH] Make oe-setup-layers efficiently idempotent

2023-01-14 Thread Chuck Wolber
destdir" to keep pace with upstream activity for those who wish to use it that way. Signed-off-by: Chuck Wolber --- scripts/oe-setup-layers | 55 + 1 file changed, 46 insertions(+), 9 deletions(-) diff --git a/scripts/oe-setup-layers b/scr

Re: [OE-core] [RFC PATCH 1/2] cargo-update-recipe-crates.bbclass: add a class to generate SRC_URI crate lists from Cargo.lock

2022-10-04 Thread Chuck Wolber
On Fri, Sep 30, 2022 at 10:55 AM Alexander Kanavin wrote: %> Snip %< > On the other hand, bitbake does not use cargo (and quite possible > won't ever be able to), > Can you elaborate on this? I only ask because we are using this[1] and this[2] to build this[3] recipe for hardknott. 1.

Re: [OE-core] [PATCH 4/5] scripts/oe-setup-layers: add a script that restores the layer configuration from a json file

2022-08-21 Thread Chuck Wolber
On Wed, Aug 17, 2022 at 6:10 AM Alexander Kanavin wrote: > This script can be used directly from poky, or can be copied directly into > a > layer or any other repository - it is self-suffucient and requires only > python3 > and git on the host where it will run. It is also copied by the >

Re: [OE-core] [PATCH 1/6] scripts/oe-setup-builddir: make it known where configurations come from

2022-07-30 Thread Chuck Wolber
On Fri, Jul 29, 2022 at 13:12 Alexander Kanavin wrote: I can do that, but I'm curious about this 80 character limit. Who > cares, in 2022, and why? I care :) Why? It is an expectation built into a lot of tools for one thing. The git commit log is one notable example. Wrapping commit messages

Re: [OE-core][kirkstone 13/15] gobject-introspection-data: Disable cache for g-ir-scanner

2022-07-28 Thread Chuck Wolber
On Thu, Jul 28, 2022 at 11:37 AM Steve Sakoman wrote: > On Thu, Jul 28, 2022 at 7:55 AM Chuck Wolber > wrote: > > > > FWIW, the gobject-introspection-native recipe was one of the "canaries > in the mine" that reliably caused an image build to die while I was >

Re: [OE-core][kirkstone 13/15] gobject-introspection-data: Disable cache for g-ir-scanner

2022-07-28 Thread Chuck Wolber
FWIW, the gobject-introspection-native recipe was one of the "canaries in the mine" that reliably caused an image build to die while I was actively encountering this GCC10 compiler issue in Hardknott: https://www.mail-archive.com/yocto@lists.yoctoproject.org/msg06163.html

[OE-core] systemd_create_users broken even more

2022-02-04 Thread Chuck Wolber
When relying on useradd-staticids, this commit [1] made the problems that this [2] bug causes, much worse. Prior to that commit we could predict with surprising accuracy what the UID and GID would be for the very small number of systemd-* accounts that were created (or simply patch the expected

Re: [OE-core] Inclusive Language Proposal for YP/OE

2022-01-25 Thread Chuck Wolber
On Mon, Jan 24, 2022 at 8:18 AM Jon Mason wrote: %< SNIP %< > Branch Names > The “master” branches on the relevant OpenEmbedded and Yocto Project > git trees will be changed to an alternative name at some point in the > future. The current preferred name is “devel”. > Why devel instead of

Re: [OE-core] [hardknott][PATCH 9/9] python3-pyelftools: fix the override syntax

2022-01-11 Thread Chuck Wolber
On Tue, Jan 11, 2022 at 06:33 Anuj Mittal wrote: > An earlier patch cherry-picked from master used : for override. Change > it to use _ for hardknott. I have been using the “:” for override in Hardknott for some time now. Why is this being reverted? ..Ch:W.. -- *"Perfection must be reached

Re: [OE-core] How to trigger Yocto Linux /etc/profile or shell scripts in /etc/profile.d without shell logging in?

2021-10-10 Thread Chuck Wolber
On Sun, Oct 10, 2021 at 9:30 PM JH wrote: > The Yocto uses /etc/profile for root login, but there is no root > physical login in an embedded device so the /etc/profile is never > called, I added a shell script to /etc/profile.d, it was not called > either. Both /etc/profile and scripts in

Re: [OE-core] Improve npm support to run build scripts

2021-10-05 Thread Chuck Wolber
On Tue, Oct 5, 2021 at 12:29 PM Konrad Weihmann wrote: > > While personally I think in the long run, every npm dependency has to be > provided as a recipe of its own (even I know the costs of that pretty > well)... esp when CVE checking and basic packaging hygiene should be > enforced. >

[OE-core] Hardknott (GCC10) Compiler Issues

2021-06-24 Thread Chuck Wolber
All, Please accept my apologies in advance for the detailed submission. I think it is warranted in this case. There is something... "odd" about the GCC 10 compiler that is delivered with Hardknott. I am still chasing it down, so I am not yet ready to declare a root cause or submit a bug, but I