Ozone integration.

mojo/BUILD.gn

 # Copyright 2014 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 import("//build/config/ui.gni")
 import("//build/module_args/mojo.gni")
 import("//mojo/public/mojo.gni")
 
 # TODO(beng): this meta target should probably move to the root dir's BUILD.gn.
 group("mojo") {
@@ skipping 32 matching lines @@
   if (is_linux) {
     deps += [ "//mojo/python" ]
   }
 
   if (mojo_use_nacl) {
     deps += [
       "//mojo/nacl:mojo_nacl",
       "//mojo/nacl:mojo_nacl_tests",
     ]
   }
+
+  if (use_ozone) {

[jamesr, 2015/08/18 20:11:33]

do we need use_ozone to be toggleable within the mojo repo? i'd like to keep the
cross-product of configurations down. will the ozone path work on our linux
boxes?

[spang, 2015/08/18 20:25:31]

Not yet, but with some work we could have an x11 platform in ozone. We also want
it in order to deprecate the OS_CHROMEOS && !USE_OZONE build.

+    deps += [
+      "//ui/ozone",
+      "//ui/ozone/demo",
+    ]
+  }
 }
 
 group("tests") {
   testonly = true
   deps = [
     "//mojo/common:mojo_common_unittests",
     "//mojo/converters/surfaces/tests:mojo_surfaces_lib_unittests",
     "//mojo/edk/system:tests",
     "//mojo/edk/test:public_tests",
     "//mojo/dart/embedder/test:dart_unittests",
@@ skipping 35 matching lines @@
       "//mojo/edk/js:tests",
       "//services/js:js_apptests",
       "//services/js:js_services_unittests",
     ]
   }
 
   if (mojo_use_prebuilt_network_service) {
     deps += [ "//mojo/public/tools:copy_network_service_apptests" ]
   }
 }