kirkstone: backport clang from scarthgap

[adalessandro]

Links:
#1023
OSSystems/meta-browser#842

---

Contributor checklist

• Changes have been tested
• Signed-off-by is present
• The PR complies with the Open Embedded Commit Patch Message Guidelines

Reviewer Guidelines

• When submitting a review, please pick:
  • 'Approve' if this change would be acceptable in the codebase (even if there are minor or cosmetic tweaks that could be improved).
  • 'Request Changes' if this change would not be acceptable in our codebase (e.g. bugs, changes that will make development harder in future, security/performance issues, etc).
  • 'Comment' if you don't feel you have enough information to decide either way (e.g. if you have major questions, or you don't understand the context of the change sufficiently to fully review yourself, but want to make a comment)

[adalessandro]

@kraj @MaxIhlenfeldt I've created this (still) work in progress PR so we can discuss on top of it:

• This PR only backports clang from scarthgap. No other recipes nor changes are backported.
• Chromium 129.0.6668.100 from meta-browser successfully builds (with a few rust backport fixes). See kirkstone: backport chromium from scarthgap OSSystems/meta-browser#843

I'd like your comments if possible:

• Is it okay to just backport the specific clang recipes part?
• The README and probably conf/nonclangable.conf files need to be updated as well. Could you help there perhaps?
• Is there a testing/CI to be used here?

[adalessandro]

* Is it okay to just backport the specific `clang` recipes part?

Regarding the above, definitely other parts in this layer (that depends on clang) need to be updated as well.

[MaxIhlenfeldt]

Will defer to kraj as I'm not too familiar with meta-clang.

[adalessandro]

@kraj whenever you have some time (I know you're busy :-) ) please give me some guidelines on how to follow up, then I can polish this up. Thanks!

[petermarko]

This will not be accepted, LTS branches do not accept major version updates.
I wonder if this could be submitted to https://git.yoctoproject.org/meta-lts-mixins/ as new branch kirkstone/clang

[adalessandro]

This will not be accepted, LTS branches do not accept major version updates. I wonder if this could be submitted to https://git.yoctoproject.org/meta-lts-mixins/ as new branch kirkstone/clang

@petermarko thanks, you're right, so I'll close this one. Just in case, do you know who should I ask? AFAICS Scott scott.murray@konsulko.com is the maintainer, but I couldn't reach him yet.

[petermarko]

Afaik each branch of mixin layers repo is maintained by someone else.
So you need to find someone willing to be the maintainer of kirkstone/clang branch or become the maintainer yourself.