Componentize chrome/browser/rlz

components/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/features.gni")
 import("//build/config/ui.gni")
 import("//testing/test.gni")
 import("//tools/grit/repack.gni")
 
 # Collection of all components. You wouldn't link to this, but this is rather
@@ skipping 289 matching lines @@
 
     # These are the deps required by the code in this target.
     "//base",
     "//base/test:test_support",
     "//content/test:test_support",
     "//net",
     "//ui/base",
     "//ui/resources:ui_test_pak",
   ]
 
+  if (enable_rlz) {
+    deps += [ "//components/rlz:unittests" ]
+  }

[Roger Tawa OOO till Jul 10th, 2015/07/02 18:22:28]

I wonder if the tests should always be compiled and run.  Is there any advantage
to no doing so?

[sdefresne, 2015/07/03 16:16:37]

Make sense. This will require changing client code to #include rlz_tracker.h
conditionally depending on ENABLE_RLZ macro instead of checking the macro in the
header though.

+
   if (is_android) {
     isolate_file = "components_unittests.isolate"
   }
 
   data_deps = [ ":components_tests_pak" ]
 
   if (is_android) {
     deps += [ "//content/public/android:content_java" ]
   }
 
@@ skipping 105 matching lines @@
 
   deps = [
     "//base",
     "//base/test:test_support_perf",
     "//testing/gtest",
     "//testing/perf",
     "//content/test:test_support",
     "//components/visitedlink/browser",
   ]
 }