On 20/01/17 12:37, Carlos Rafael Giani wrote:
> Looks okay overall. A few details need to be addressed:
>
Thank you again for the review. I've sent a new version of the patch to
the ML, addressing your comments.
Best,
--
Jacobo Aragunde
Software Engineer at Igalia
--
__
On 20/01/17 12:37, Carlos Rafael Giani wrote:
> Looks okay overall. A few details need to be addressed:
> ...
Thanks for your feedback, Carlos. I will submit a modified patch soon.
> Besides that, how is the performance of Chromium 53 with Ozone-Wayland?
> Any improvements over 48? What platform
Looks okay overall. A few details need to be addressed:
1) In the .bb file, change "# Component build is unsupported in
ozone-wayland for Chromium 48" to "# Component build is unsupported in
ozone-wayland for Chromium 53"
2) Diffs in the patches like this can be confusing:
chromium-48
That is the latest version of Chromium that has been made work with
the Ozone-Wayland project.
Patches have been rebased and configure flags were changed because
existing ones were causing conflicts in the new version. An extra
patch was added to prevent the build from failing when building
withou
