-
Maksim Sisov authored
We need to avoid using non-Ozone/X11 code when OzonePlatform feature is enabled for Linux once use_x11 && use_ozone are set together. ----- PS: Please note that this is a temp solution that will help to choose between ozone and non-ozone X11 build. The switch that will be used to choose the path is --enable-features=UseOzonePlatform. Once non-Ozone X11 path is removed (hopefully by Q1 2021 depending on how th finch trial goes), the wrapper will be removed. Please also note that it's impossible to build use_x11 && use_ozone without some hacks in PlatformCursor code. The changes to that are on their way to upstream. ---- Bug: 1085700 Change-Id: Ia1b9234cffdd6e40e50f39a6e35900c9f42e221e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315685Reviewed-by:
Miguel Casas <mcasas@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
mark a. foltz <mfoltz@chromium.org> Reviewed-by:
David Staessens <dstaessens@chromium.org> Commit-Queue: Maksim Sisov (GMT+3) <msisov@igalia.com> Cr-Commit-Position: refs/heads/master@{#796411}
40c1c95a