Migrate weave-related classes from proximity_auth/ble to cryptauth/ble.

components/cryptauth/BUILD.gn

Index: components/cryptauth/BUILD.gn
diff --git a/components/cryptauth/BUILD.gn b/components/cryptauth/BUILD.gn
index 1bfdc1ba76a2b72eb2defb411ac1c7bd877dfaba..811d78d1cf9e11f2b8ec162bd224015302696599 100644
--- a/components/cryptauth/BUILD.gn
+++ b/components/cryptauth/BUILD.gn
@@ -47,6 +47,7 @@ static_library("cryptauth") {
 
   deps = [
     "//base",
+    "//components/cryptauth/ble",
     "//components/gcm_driver",
     "//components/gcm_driver/common",
     "//components/prefs",
@@ -59,6 +60,9 @@ static_library("cryptauth") {
   public_deps = [
     "//components/cryptauth/proto",
   ]
+
+  # TODO (hansberry): Resolve this.
+  allow_circular_includes_from = [ "//components/cryptauth/ble" ]

[Kyle Horimoto, 2016/12/08 21:52:40]

What is your plan for resolving this and the other circular dependencies?

[Kyle Horimoto, 2016/12/09 01:25:09]

Ping.

[Ryan Hansberry, 2016/12/09 02:36:50]

I see two ways to solve this:

1) Consolidate all of these migrated classes from proximity_auth into a single
subdirectory (called 'connection/' or something like that)

2) Maintain the new cryptauth/ble/ directory, and place the classes it depends
on within root cryptauth/ into a subdirectory, something like
'cryptauth/connection'.

Do you like either of these methods or have another idea?

[Kyle Horimoto, 2016/12/09 18:07:46]

Cool, those both sound reasonable. No need to do it in this CL, though...it's
already gotten pretty big. Thanks!

[Ryan Hansberry, 2016/12/09 20:11:05]

Great. I'll do that right after this CL.

 }
 
 static_library("test_support") {