New thin layer of API extension chrome.i18n.detectLanguage

chrome/browser/extensions/api/api_registration.gyp

Index: chrome/browser/extensions/api/api_registration.gyp
diff --git a/chrome/browser/extensions/api/api_registration.gyp b/chrome/browser/extensions/api/api_registration.gyp
index 458126fb4840d8047c0f29b08c829339268b1609..6fbfd9fa3b9a98982317c3890ba07ffb7daee321 100644
--- a/chrome/browser/extensions/api/api_registration.gyp
+++ b/chrome/browser/extensions/api/api_registration.gyp
@@ -35,6 +35,12 @@
             '<(DEPTH)/chrome/chrome.gyp:drive_proto',
           ],
         }],
+        [ 'cld_version==0 or cld_version==2', {

[Ken Rockot(use gerrit already), 2015/07/21 22:28:39]

nit: no need for the space after [ 

[amalika, 2015/07/21 22:40:56]

Done.

+          'dependencies': [
+            # Interactive tests should use whatever CLD2 data access mode that
+            # the application embedder is using.
+            '<(DEPTH)/third_party/cld_2/cld_2.gyp:cld2_platform_impl', ],
+        }],

[Ken Rockot(use gerrit already), 2015/07/21 22:28:39]

i don't really know anything about CLD. I wonder if it's also a good idea to add
a clause for version 1, something like this:

    ['cld_version==1', {
      'dependencies': [
        '<(DEPTH)/third_party/cld/cld.gyp:cld',
      },
    }],

[amalika, 2015/07/21 22:40:56]

As of November 20, 2014 the sole remaining platform using CLD1 is Android. Our
API is only available on desktop. 
In i18n.cc file we also only have support for CLD2 as per reason above, so I
guess it would be unnecessary to add a dependency for CLD1?

       ],
     },
   ],