Enable proguard for ChromeShell

chrome/chrome_shell.gypi

 # Copyright 2014 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.
 
 # This GYPI allows independent customization of the chrome shell in a manner
 # similar to content shell (in content_shell.gypi). Notably, this file does
 # NOT contain chrome_android_core, which is independent of the chrome shell
 # and should be separately customized.
 {
   'variables': {
@@ skipping 89 matching lines @@
         'apk_name': 'ChromeShell',
         'android_manifest_path': '<(SHARED_INTERMEDIATE_DIR)/chrome_shell_manifest/AndroidManifest.xml',
         'native_lib_version_name': '<(version_full)',
         'java_in_dir': 'android/shell/java',
         'resource_dir': 'android/shell/res',
         'asset_location': '<(PRODUCT_DIR)/../assets/<(package_name)',
         'native_lib_target': 'libchromeshell',
         'additional_input_paths': [
           '<@(chrome_android_pak_output_resources)',
         ],
+        'proguard_enabled': 'true',
+        'proguard_flags_paths': ['android/shell/java/proguard.flags'],
       },
       'includes': [ '../build/java_apk.gypi', ],
     },
     {
       # GN: N/A
       # chrome_shell_apk creates a .jar as a side effect. Any java targets
       # that need that .jar in their classpath should depend on this target,
       # chrome_shell_apk_java. Dependents of chrome_shell_apk receive its
       # jar path in the variable 'apk_output_jar_path'.
       # This target should only be used by targets which instrument
@@ skipping 51 matching lines @@
       'target_name': 'chrome_sync_shell_apk_java',
       'type': 'none',
       'dependencies': [
         'chrome_sync_shell_apk',
       ],
       'includes': [ '../build/apk_fake_jar.gypi' ],
     },
   ],
 
 }