-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chromium: kirkstone: Update to Chromium 130 #842
Comments
From @MaxIhlenfeldt #716 (comment):
Agreed, the best approach here might be backporting from scarthgap, which currently provides clang |
@MaxIhlenfeldt BTW, have there been any effort on using the prebuilt clang toolchain (shipped along the chromium sources) instead of |
I think @kraj probably knows the reason we're not using the prebuilt toolchain. |
@MaxIhlenfeldt is there a specific |
scarthgap support is maintained on the |
AFAICS, the prebuilt toolchain that is shipped along the chromium package comes in fact prebuilt and expects the sysroot to include several header and libraries. Their build system then pulls a prepacked debian image for that purpose, but pointing that to the yocto sysroot would imply getting any missing header/lib the toolchain needs or install there. @kraj that's my understanding from what I could see. Let me know if you agree or have other insights. |
Yocto Kirkstone is LTS (until Apr. 2026) but due to its dependency on
meta-clang
[0], the chromium version is freezed at120.0.6099.224
.This issue is to keep track of ongoing efforts on updating Chromium in Kirkstone.
Note that Chromium 130 [1] has been released and version will get bumped in
master
[2].As part of this task,
meta-clang
needs to backportclang >= 16
to kirkstone, see comment #716 (comment)[0] #716
[1] https://chromereleases.googleblog.com/2024/10/stable-channel-update-for-desktop_15.html
[2] #841
The text was updated successfully, but these errors were encountered: