[Android] Makes GYP changes for EMMA coverage

android_webview/android_webview.gyp

 # Copyright 2009 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.
 {
   'variables': {
     'chromium_code': 1,
   },
   'includes': [
     'android_webview_tests.gypi',
   ],
@@ skipping 182 matching lines @@
       'target_name': 'android_webview_java',
       'type': 'none',
       'dependencies': [
         '../components/components.gyp:navigation_interception_java',
         '../components/components.gyp:web_contents_delegate_android_java',
         '../content/content.gyp:content_java',
         '../ui/ui.gyp:ui_java',
       ],
       'variables': {
         'java_in_dir': '../android_webview/java',
+        'emma_should_instrument': 1,

[cjhopman, 2013/08/21 17:37:48]

Hm, I still don't like having to manually mark each library as allowing
instrumenting. Is there much cost to instrumenting libraries when we don't need
to? We could guard it on <(chromium_code) so that it isn't used for third_party
libraries.

If there is significant cost to that, then this is fine. 

The name implies that setting this to 1 enables emma instrumentation, but it
also depends on <(emma_coverage). If you can think of a name that makes that
clear, that would be great, but isn't required.

[gkanwar1, 2013/08/21 18:28:32]

Ah I didn't notice the chromium_code variable before. Instrumenting all java
libs with that variable set actually sounds perfect. I'm going to switch over to
that.

       },
       'includes': [ '../build/java.gypi' ],
     },
   ],
 }