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

kirkstone: Backport from scarthgap #1023

Closed
adalessandro opened this issue Oct 21, 2024 · 3 comments
Closed

kirkstone: Backport from scarthgap #1023

adalessandro opened this issue Oct 21, 2024 · 3 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.

Issue OSSystems/meta-browser#842 keeps track of ongoing efforts on updating Chromium in Kirkstone.

See comment OSSystems/meta-browser#716 (comment):

[...] 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.

meta-clang scarthgap currently provides clang 18.1.6, so backporting from it seems to be the best path here.

[0] OSSystems/meta-browser#716

@adalessandro
Copy link
Author

Pushed WIP branch backporting from scarthgap: https://github.com/adalessandro/meta-clang/tree/wip/adalessandro/kirkstone-backport-scarthgap
Building clang-native recipe, passed.

@adalessandro
Copy link
Author

@kraj is there some sort of pipeline to build/test different configurations?

@adalessandro
Copy link
Author

Closing in favor of #1040

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

No branches or pull requests

1 participant