[ios] Adds support for parsing Text-to-Speech search results.

ios/chrome/browser/ui/voice/BUILD.gn

Index: ios/chrome/browser/ui/voice/BUILD.gn
diff --git a/ios/chrome/browser/ui/voice/BUILD.gn b/ios/chrome/browser/ui/voice/BUILD.gn
new file mode 100644
index 0000000000000000000000000000000000000000..3093d63d63833915d05ca4a34a39229ec793d245
--- /dev/null
+++ b/ios/chrome/browser/ui/voice/BUILD.gn
@@ -0,0 +1,39 @@
+# Copyright 2015 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.
+
+source_set("tts") {

[sdefresne, 2016/10/25 13:20:30]

I would call this "voice" or change the directory name to "tts", unless you plan
to also have non "tts" related code in that directory (as there is in
//ios/chrome/browser/voice, but then maybe the code should be moved to
//ios/chrome/browser/tts too).

[rohitrao (ping after 24h), 2016/10/25 15:23:12]

Done.

In general, the "tts" code is going into separate targets to avoid breaking the
downstream build.  But for this specific case, the target should just be named
"voice" to start with.

+  sources = [
+    "text_to_speech_player.h",
+    "text_to_speech_player.mm",
+    "voice_search_notification_names.h",
+    "voice_search_notification_names.mm",
+  ]
+
+  deps = [
+    "//base",
+  ]
+
+  libs = [ "AVFoundation.framework" ]
+}
+
+source_set("tts_unit_tests") {

[sdefresne, 2016/10/25 13:20:30]

We usually just call those targets "unit_tests" as the full name will be
//ios/chrome/browser/ui/voice:unit_tests which make it easy to understand what
this is testing.

[rohitrao (ping after 24h), 2016/10/25 15:23:12]

Done.

+  testonly = true
+
+  sources = [
+    "text_to_speech_player_unittest.mm",
+  ]
+
+  deps = [
+    "//base",
+    "//base/test:test_support",
+    "//ios/web",
+    "//ios/web:test_support",
+    "//testing/gtest",
+    "//url",
+  ]
+
+  public_deps = [
+    ":tts",
+  ]
+}