-
Notifications
You must be signed in to change notification settings - Fork 186
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
Ozone/Wayland: Update branch to version 71.0.3545.0 aka ToT #170
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for updating the recipe and keeping working on this important feature. I did send few requests for changes to keep the level of quality of our metadata but so far it looks very good.
Please do those adjustment and force push it to the very same branch so we can do a new review.
Thanks in advance
...omium/chromium-ozone-wayland/0001-Fix-GCC-build-remove-constexpr-for-non-resolved-comp.patch
Outdated
Show resolved
Hide resolved
...r/chromium/chromium-ozone-wayland/0001-Fix-a-GCC-error-about-undeclared-std-unique_ptr.patch
Outdated
Show resolved
Hide resolved
...omium/chromium-ozone-wayland/0001-OmniboxTextView-fix-gcc-error-for-structure-initiali.patch
Outdated
Show resolved
Hide resolved
...omium/chromium-ozone-wayland/0001-ScrollPaintPropertyNode-Rename-SnapContainerData-to-.patch
Outdated
Show resolved
Hide resolved
...ser/chromium/chromium-ozone-wayland/0001-ozone-wayland-Fix-fpermissive-problem-for-GCC.patch
Outdated
Show resolved
Hide resolved
please review again |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is closer. The field used is wrong though. Please see the comment I made.
...omium/chromium-ozone-wayland/0001-Fix-GCC-build-remove-constexpr-for-non-resolved-comp.patch
Outdated
Show resolved
Hide resolved
...omium/chromium-ozone-wayland/0001-Fix-GCC-build-remove-constexpr-for-non-resolved-comp.patch
Outdated
Show resolved
Hide resolved
The branch is based on a weekly-rebased repo located at github.com/Igalia/chromium Test-built with: * Yocto sumo, GCC 7 and MACHINE="raspberrypi3" Signed-off-by: Maksim Sisov <msisov@igalia.com>
@rakuco ping |
Sorry for the delay, I'll try to take a look at the PR tomorrow. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, thanks for addressing the comments from #156 as well!
The branch is based on a weekly-rebased repo located at github.com/Igalia/chromium
Currently, around 85% of patches are upstreamed. We've reworked the design of the ozone/wayland
and it's no longer based on mus aka ui service. The work can be tracked from the ToT crbug -
https://bugs.chromium.org/p/chromium/issues/detail?id=578890
We ported various patches to the newest design and re implemented many features. It's hard to say
the exact changes now, but this recipe is a ground to support a multiprocess mode with all the possible
wayland performance features including: frame callback, presentation feedback, partial swap, native
gpu memory buffers and etc. Though, the chromium in this recipe is built with all these features enabled,
the browser is run with --in-process-gpu flag. The reason behind this is lack of certain patches and optimizations, which I don't want to publish yet. I will update them soon.
Test-built with:
It's hard to describe why licences changed as long as the last version of the browser was
m64, which is 7 milestones behind the current m71 milestone.
Removed licence files:
The explanations are taken from the last commit messages:
Changed licence files:
zlib-aarch64.patch is now added to chromium-gn, but oe-clang patch had to be rebased and is not compatible with chromium m68. Thus, there is a different patch for chromium m71
Signed-off-by: Maksim Sisov msisov@igalia.com