Gtk3 ui: Add libgtk3ui as a separate build component

chrome/browser/BUILD.gn

Index: chrome/browser/BUILD.gn
diff --git a/chrome/browser/BUILD.gn b/chrome/browser/BUILD.gn
index eeb861e22c622b4defaac1402068d876e2686f2b..b21e8c000cb1b4847f9e8a4781852dfe17b489f3 100644
--- a/chrome/browser/BUILD.gn
+++ b/chrome/browser/BUILD.gn
@@ -2237,8 +2237,11 @@ split_static_library("browser") {
     ]
   }
   if (use_aura && !use_ozone && is_desktop_linux) {
-    deps += [ "//chrome/browser/ui/libgtk2ui" ]
-    allow_circular_includes_from += [ "//chrome/browser/ui/libgtk2ui" ]
+    if (use_gtk3) {
+      deps += [ "//chrome/browser/ui/libgtkui:libgtk3ui" ]
+    } else {
+      deps += [ "//chrome/browser/ui/libgtkui:libgtk2ui" ]
+    }
   }
   if (is_posix && !is_mac) {
     sources += [
@@ -3963,6 +3966,12 @@ if (is_win) {
   }
 }
 
+source_set("theme_properties") {

[Dirk Pranke, 2016/10/26 19:09:43]

Is libgtkui the only thing that depends on this? Is it possible to move the
header into that directory then, or is that a bad idea?

[Tom (Use chromium acct), 2016/10/26 22:10:57]

I changed some things around related to theme_properties in
chrome/browser/BUILD.gn and chrome/browser/ui/libgtkui/BUILD.gn. dpranke@ PTAL

+  sources = [
+    "themes/theme_properties.h",
+  ]
+}
+
 proto_library("resource_prefetch_predictor_proto") {
   sources = [
     "predictors/resource_prefetch_predictor.proto",