GN: Move boringssl_tests into build_with_chromium condition

third_party/boringssl/BUILD.gn

Index: third_party/boringssl/BUILD.gn
diff --git a/third_party/boringssl/BUILD.gn b/third_party/boringssl/BUILD.gn
index d4f00cfe726d3fbcbb0f3b8a0dddc1604ee5dfce..fe2515c6d0955db370c4944dc58c57e33a0e2176 100644
--- a/third_party/boringssl/BUILD.gn
+++ b/third_party/boringssl/BUILD.gn
@@ -125,14 +125,14 @@ component("boringssl") {
   }
 }
 
-create_tests("boringssl_tests") {
-  configs = [ ":internal_config" ]
-  deps = [
-    ":boringssl",
-  ]
-}
-
 if (build_with_chromium) {
+  create_tests("boringssl_tests") {

[davidben, 2016/04/27 17:16:16]

I think the root problem here is I forget the annoying configs -= chromium_code
/ configs += no_chromium_code lines here. Do you mind putting that in? That will
suppress the warning which matches how Chromium builds the rest of BoringSSL and
how BoringSSL builds itself. Though I should maybe see about making us
chromium_code-clean if it's considered kosher for //third_party bits to use it.

I'll defer to you whether you want to continue suppressing the tests. There's no
reason they shouldn't be able to build, but it's also true they're not being
used.

[kjellander_chromium, 2016/04/27 20:07:21]

I prefer you do that in a separate CL. My main objective here is to not compile
the tests at all when we build the default (all) target for GN in WebRTC. In
order to do so, this is the only way AFAIK.

[davidben, 2016/04/27 22:52:31]

Sounds good. I'll deal with that separately then. lgtm.

+    configs = [ ":internal_config" ]
+    deps = [
+      ":boringssl",
+    ]
+  }
+
   test("boringssl_unittests") {
     deps = [
       ":boringssl_tests",