Skip to content
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

Open
adalessandro opened this issue Oct 21, 2024 · 6 comments
Open

chromium: kirkstone: Update to Chromium 130 #842

adalessandro opened this issue Oct 21, 2024 · 6 comments

Comments

@adalessandro
Copy link

Yocto Kirkstone is LTS (until Apr. 2026) but due to its dependency on meta-clang [0], the chromium version is freezed at 120.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 backport clang >= 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

@adalessandro
Copy link
Author

From @MaxIhlenfeldt #716 (comment):

Thanks for looking into this! Note that clang 16 is the bare minimum we need to build Chromium, but that might change again (or might have changed already since the last time we built kirkstone). Thus, having clang 17 or 18 (scarthgap uses 18) would be even better. Not sure how much more work it'd be to backport clang 18?

Agreed, the best approach here might be backporting from scarthgap, which currently provides clang 18.1.6.

@adalessandro
Copy link
Author

@MaxIhlenfeldt BTW, have there been any effort on using the prebuilt clang toolchain (shipped along the chromium sources) instead of clang-native? Not sure if that's even possible.

@MaxIhlenfeldt
Copy link
Collaborator

I think @kraj probably knows the reason we're not using the prebuilt toolchain.

@adalessandro
Copy link
Author

adalessandro commented Oct 21, 2024

@MaxIhlenfeldt is there a specific scarthgap branch in meta-browser? Or is it just master?

@MaxIhlenfeldt
Copy link
Collaborator

MaxIhlenfeldt commented Oct 22, 2024

scarthgap support is maintained on the master branch. kirkstone only has its own branch because we stopped supporting it on master.

@adalessandro
Copy link
Author

adalessandro commented Oct 22, 2024

I think @kraj probably knows the reason we're not using the prebuilt toolchain.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants