1 # Copyright 2014 The Chromium Authors. All rights reserved.
2 # Use of this source code is governed by a BSD-style license that can be
3 # found in the LICENSE file.
5 # This GYPI allows independent customization of the chrome shell in a manner
6 # similar to content shell (in content_shell.gypi). Notably, this file does
7 # NOT contain chrome_android_core, which is independent of the chrome shell
8 # and should be separately customized.
11 'package_name': 'chrome_shell_apk',
15 # GN: //chrome/android:chrome_shell_base
16 'target_name': 'libchromeshell_base',
19 '../base/base.gyp:base',
20 'chrome_android_core',
21 'chrome.gyp:browser_ui',
22 '../content/content.gyp:content_app_both',
24 'direct_dependent_settings': {
26 # Some android targets still depend on --gc-sections to link.
27 # TODO: remove --gc-sections for Debug builds (crbug.com/159847).
32 [ 'order_profiling!=0', {
33 'dependencies': [ '../tools/cygprofile/cygprofile.gyp:cygprofile', ],
35 [ 'use_allocator!="none"', {
37 '../base/allocator/allocator.gyp:allocator', ],
39 [ 'cld_version==0 or cld_version==2', {
41 # Chrome shell should always use the statically-linked CLD data.
42 '<(DEPTH)/third_party/cld_2/cld_2.gyp:cld2_static', ],
47 # GN: //chrome/android:chrome_shell
48 'target_name': 'libchromeshell',
49 'type': 'shared_library',
51 'android/shell/chrome_shell_entry_point.cc',
52 'android/shell/chrome_main_delegate_chrome_shell_android.cc',
53 'android/shell/chrome_main_delegate_chrome_shell_android.h',
56 'libchromeshell_base',
59 # File 'protection' is based on non-trivial linker magic. TODO(pasko):
60 # remove it when crbug.com/424562 is fixed.
61 '../base/files/protect_file_posix.gypi',
65 # GN: //chrome/android:chrome_sync_shell
66 'target_name': 'libchromesyncshell',
67 'type': 'shared_library',
69 'android/shell/chrome_shell_entry_point.cc',
70 'android/sync_shell/chrome_main_delegate_chrome_sync_shell_android.cc',
71 'android/sync_shell/chrome_main_delegate_chrome_sync_shell_android.h',
74 'libchromeshell_base',
75 '../sync/sync.gyp:test_support_sync_fake_server_android',
79 # GN: //chrome/android:chrome_shell_manifest
80 'target_name': 'chrome_shell_manifest',
83 'jinja_inputs': ['android/shell/java/AndroidManifest.xml.jinja2'],
84 'jinja_output': '<(SHARED_INTERMEDIATE_DIR)/chrome_shell_manifest/AndroidManifest.xml',
86 'includes': [ '../build/android/jinja_template.gypi' ],
89 # GN: //chrome/android:chrome_shell_apk
90 'target_name': 'chrome_shell_apk',
94 'chrome_android_paks_copy',
96 '../media/media.gyp:media_java',
99 'apk_name': 'ChromeShell',
100 'android_manifest_path': '<(SHARED_INTERMEDIATE_DIR)/chrome_shell_manifest/AndroidManifest.xml',
101 'native_lib_version_name': '<(version_full)',
102 'java_in_dir': 'android/shell/java',
103 'resource_dir': 'android/shell/res',
104 'asset_location': '<(PRODUCT_DIR)/../assets/<(package_name)',
105 'native_lib_target': 'libchromeshell',
106 'additional_input_paths': [
107 '<@(chrome_android_pak_output_resources)',
110 'includes': [ '../build/java_apk.gypi', ],
114 # chrome_shell_apk creates a .jar as a side effect. Any java targets
115 # that need that .jar in their classpath should depend on this target,
116 # chrome_shell_apk_java. Dependents of chrome_shell_apk receive its
117 # jar path in the variable 'apk_output_jar_path'.
118 # This target should only be used by targets which instrument
120 'target_name': 'chrome_shell_apk_java',
125 'includes': [ '../build/apk_fake_jar.gypi' ],
128 # GN: //chrome/android:chrome_sync_shell_manifest
129 'target_name': 'chrome_sync_shell_manifest',
132 'jinja_inputs': ['android/sync_shell/java/AndroidManifest.xml.jinja2'],
133 'jinja_output': '<(SHARED_INTERMEDIATE_DIR)/chrome_sync_shell_manifest/AndroidManifest.xml',
135 'includes': [ '../build/android/jinja_template.gypi' ],
138 # GN: //chrome/android:chrome_sync_shell_apk
139 'target_name': 'chrome_sync_shell_apk',
143 'chrome_android_paks_copy',
144 'libchromesyncshell',
145 '../media/media.gyp:media_java',
146 '../sync/sync.gyp:sync_java_test_support',
149 'apk_name': 'ChromeSyncShell',
150 'android_manifest_path': '<(SHARED_INTERMEDIATE_DIR)/chrome_sync_shell_manifest/AndroidManifest.xml',
151 'R_package': 'org.chromium.chrome.shell',
152 'native_lib_version_name': '<(version_full)',
153 'java_in_dir': 'android/shell/java',
154 'resource_dir': 'android/shell/res',
155 'asset_location': '<(PRODUCT_DIR)/../assets/<(package_name)',
156 'native_lib_target': 'libchromesyncshell',
157 'additional_input_paths': [
158 '<@(chrome_android_pak_output_resources)',
161 'includes': [ '../build/java_apk.gypi', ],
165 # chrome_sync_shell_apk creates a .jar as a side effect. Any java
166 # targets that need that .jar in their classpath should depend on this
167 # target. Dependents of chrome_sync_shell_apk receive its jar path in the
168 # variable 'apk_output_jar_path'. This target should only be used by
169 # targets which instrument chrome_sync_shell_apk.
170 'target_name': 'chrome_sync_shell_apk_java',
173 'chrome_sync_shell_apk',
175 'includes': [ '../build/apk_fake_jar.gypi' ],