Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(2621)

Unified Diff: build/java_apk.gypi

Issue 10914130: Make apks be built in a consistent way (Closed) Base URL: http://git.chromium.org/chromium/src.git@ant_ijpforrealz
Patch Set: Created 8 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | content/content_shell.gypi » ('j') | content/content_shell.gypi » ('J')
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: build/java_apk.gypi
diff --git a/build/java_apk.gypi b/build/java_apk.gypi
new file mode 100644
index 0000000000000000000000000000000000000000..32c817c7c47f1bd7ffbef47233c734441c21d8db
--- /dev/null
+++ b/build/java_apk.gypi
@@ -0,0 +1,75 @@
+# Copyright (c) 2012 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 file is meant to be included into a target to provide a rule
+# to build Java in a consistent manner.
Ted C 2012/09/07 20:21:10 s/Java/an Android APK
cjhopman 2012/09/07 20:52:36 Done.
+#
+# To use this, create a gyp target with the following form:
+# {
+# 'target_name': 'my-package_apk',
Ted C 2012/09/07 20:21:10 is the underscore important before the apk? Just
cjhopman 2012/09/07 20:52:36 The target name isn't actually important. The _apk
+# 'type': 'none',
+# 'variables': {
+# 'package_name': 'my_package',
+# 'apk_name': 'MyPackage',
+# 'java_in_dir': 'path/to/package/root',
+# 'resource_dir': 'path/to/package/root/res',
+# },
+# 'includes': ['path/to/this/gypi/file'],
+# }
+#
+# Note that this assumes that there's an ant buildfile <package_name>_apk.xml in
+# java_in_dir. So, if you have package_name="content_shell" and
+# java_in_dir="content/shell/android/java" you should have a directory structure
+# like:
+#
+# content/shell/android/java/content_shell_apk.xml
+# content/shell/android/java/src/chromium/base/Foo.java
+# content/shell/android/java/src/chromium/base/Bar.java
+
+{
+ 'variables': {
+ 'input_jars_paths': [],
+ 'native_libs_paths': [],
+ 'additional_src_dirs': [],
+ 'additional_input_paths': [],
+ },
+ 'actions': [
+ {
+ 'action_name': 'ant_<(package_name)_apk',
+ 'message': 'Building <(package_name) apk.',
+ 'inputs': [
+ '<(java_in_dir)/<(package_name)_apk.xml',
+ '<(java_in_dir)/AndroidManifest.xml',
+ '<(DEPTH)/build/android/ant/common.xml',
+ '<(DEPTH)/build/android/ant/sdk-targets.xml',
+ '<!@(find <(java_in_dir) -name "*.java")',
+ '<!@(find <(resource_dir) -name "*")',
Ted C 2012/09/07 20:21:10 is resource_dir ever different from <(java_in_dir)
+ '>@(input_jars_paths)',
+ '>@(native_libs_paths)',
+ '>@(additional_input_paths)',
+ ],
+ 'outputs': [
+ '<(PRODUCT_DIR)/<(package_name)/<(apk_name)-debug.apk',
+ ],
+ 'action': [
+ 'ant',
+ '-DPRODUCT_DIR=<(ant_build_out)',
+ '-DAPP_ABI=<(android_app_abi)',
+ '-DANDROID_GDBSERVER=<(android_gdbserver)',
+ '-DANDROID_SDK=<(android_sdk)',
+ '-DANDROID_SDK_ROOT=<(android_sdk_root)',
+ '-DANDROID_SDK_TOOLS=<(android_sdk_tools)',
+ '-DANDROID_SDK_VERSION=<(android_sdk_version)',
+ '-DANDROID_TOOLCHAIN=<(android_toolchain)',
+ '-DPACKAGE_NAME=<(package_name)',
+ '-DCONFIGURATION_NAME=<(CONFIGURATION_NAME)',
+ '-DINPUT_JARS_PATHS=>(input_jars_paths)',
+ '-DADDITIONAL_SRC_DIRS=>(additional_src_dirs)',
+ '-DRESOURCE_DIR=<(resource_dir)',
+ '-buildfile',
+ '<(java_in_dir)/<(package_name)_apk.xml'
+ ]
+ },
+ ],
+}
« no previous file with comments | « no previous file | content/content_shell.gypi » ('j') | content/content_shell.gypi » ('J')

Powered by Google App Engine
This is Rietveld 408576698