ozone/wayland: allow to run Wayland without mojo.

Even though we set require_mojo to true in the PlatformProperties,
in certain scenarios Ozone might be initialized without mojo, but in
a single process mode (for example, unittests, ozone_demo).

In this case, we should instantiate a direct connection between
buffer managers without mojo. I could use base::TaskEnvironment, but
it will require too much changes to how different tests are initialized.

For example, binding an interface and sending a mojo call requires a
a task runner handle (installed in WaylandBufferManagerGpu). And
that fails with compositor_unittests - some tests create
TaskEnvironment, and some don't.

Initializing the TaskEnvironment in CompositorTestSuite won't help,
because (as I said) some tests do that. This results in crashing when
tls delegate is set.

Bug: 1067156
Change-Id: If3236f9604c692b4ed6efc5dbaf9cc67ce36d62e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2128111
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Commit-Queue: Maksim Sisov <msisov@igalia.com>
Cr-Commit-Position: refs/heads/master@{#756173}
23 files changed
tree: 03e31d2563bd717e03e59bfc676653e83c67a866
  1. .clang-format
  2. .clang-tidy
  3. .eslintrc.js
  4. .git-blame-ignore-revs
  5. .gitattributes
  6. .gitignore
  7. .gn
  8. .vpython
  9. .vpython3
  10. .yapfignore
  11. AUTHORS
  12. BUILD.gn
  13. CODE_OF_CONDUCT.md
  14. DEPS
  15. ENG_REVIEW_OWNERS
  16. LICENSE
  17. LICENSE.chromium_os
  18. OWNERS
  19. PRESUBMIT.py
  20. PRESUBMIT_test.py
  21. PRESUBMIT_test_mocks.py
  22. README.md
  23. WATCHLISTS
  24. android_webview/
  25. apps/
  26. ash/
  27. base/
  28. build/
  29. build_overrides/
  30. buildtools/
  31. cc/
  32. chrome/
  33. chromecast/
  34. chromeos/
  35. cloud_print/
  36. codereview.settings
  37. components/
  38. content/
  39. courgette/
  40. crypto/
  41. dbus/
  42. device/
  43. docs/
  44. extensions/
  45. fuchsia/
  46. gin/
  47. google_apis/
  48. google_update/
  49. gpu/
  50. headless/
  51. infra/
  52. ios/
  53. ipc/
  54. jingle/
  55. media/
  56. mojo/
  57. native_client_sdk/
  58. net/
  59. pdf/
  60. ppapi/
  61. printing/
  62. remoting/
  63. rlz/
  64. sandbox/
  65. services/
  66. skia/
  67. sql/
  68. storage/
  69. styleguide/
  70. testing/
  71. third_party/
  72. tools/
  73. ui/
  74. url/
  75. weblayer/
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.