X11 and ozone: fix compositor_unittests
The use_x11 && use_ozone config breaks compositor_unittests. Basically, we need to decide on runtime what test compositor host we need to use - X11 or Ozone. This CL fixes that using the same approach I used in other CLs. For example, https://crrev.com/c/2247719 ----- 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 the 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: Id5442da33def3cdf8f00deffc59e11d76dbf60a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2335284Reviewed-by:Scott Violet <sky@chromium.org> Commit-Queue: Maksim Sisov (GMT+3) <msisov@igalia.com> Cr-Commit-Position: refs/heads/master@{#796351}
Showing
Please register or sign in to comment