OSSystems / meta-browser

OpenEmbedded/Yocto BSP layer for Web Browsers
MIT License
183 stars 189 forks source link

chromium: update to 116.0.5845.179 #750

Closed MaxIhlenfeldt closed 11 months ago

MaxIhlenfeldt commented 11 months ago

chromium: update to 116.0.5845.179

Release notes: https://chromereleases.googleblog.com/2023/08/stable-channel-update-for-desktop_15.html https://chromereleases.googleblog.com/2023/08/chrome-desktop-stable-update.html https://chromereleases.googleblog.com/2023/08/stable-channel-update-for-desktop_29.html https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop.html

Build and patch changes:

Drop 0023-Backport-IWYU-for-translate-TranslateUILanguagesMana.patch and 0029-Backport-IWYU-for-translate-TranslateUiLanguagesMana.patch as they are included upstream now.

Update 0020-Revert-__attribute__-and-alignas-changes.patch to omit the [[clang::noinline]] and [[clang::always_inline]] attributes. They aren't recognized by clang 14 and generate lots of warnings cluttering the logs.

Add some more build error fixes to 0021-Add-missing-typename-s.patch.

Remove one build error fix from 0034-Avoid-parenthesized-initialization-of-aggregates.patch that isn't needed any more due to upstream changes, and add a few new ones.

Add 0036-Avoid-std-ranges-find_if.patch to fix build errors with clang < 16.

Add 0037-Fix-constexpr-variable-cannot-have-non-literal-type-.patch to fix build errors with clang < 16.

Add 0038-Fix-undefined-symbol-PaintOpWriter-SerializedSize-un.patch to fix a build/linker error with clang 14.

Rebase remaining patches.

License changes:

Added licenses:

Removed licenses: none.

Updated licenses:

Test-built (big thanks to @nrpt-m):

** Please note that Chromium requires below set-up when on dunfell branch.

MaxIhlenfeldt commented 11 months ago

@rakuco as this builds upon #741, I had to include that in this PR. The actual changes introduced by this PR are in this commit.

@nrpt-m as always, testing would be greatly appreciated!

nrpt-m commented 11 months ago

@MaxIhlenfeldt @rakuco Have completed the builds & testing in master branch for all these below systems and chromium worked well in all these systems.

** @rwmacleod is away this week so, have just built rpi4 image but didn't test it. I don't have rpi4 setup so, checking with my colleagues for testing rpi4 image and once done will update here.

Next, starting with kirkstone, dunfell & mickledore branches.

nrpt-m commented 11 months ago

@MaxIhlenfeldt @rakuco Have completed the builds & testing in kirkstone and dunfell branches for all these below systems and chromium worked well in all these systems.

** Successfully built the rpi4 images but haven't tested yet on RPI4.

Next, starting with mickledore branch.

nrpt-m commented 11 months ago

@MaxIhlenfeldt @rakuco Have completed the builds & testing in mickledore branch as well for all these below systems and chromium worked well in all these systems.

chromium-ozone-wayland: qemux86-64

chromium-x11: qemux86-64, qemuarm, qemuarm64, raspberrypi4-64**

** Successfully built the rpi4 image but haven't tested yet on RPI4.

rakuco commented 11 months ago

Thanks @nrpt-m!

I've rebased this PR on top of master and adjusted the commit and PR messages to include your test results. Time to merge!