summaryrefslogtreecommitdiffstats
path: root/build/android/empty_proguard.flags
diff options
context:
space:
mode:
authorcjhopman@chromium.org <cjhopman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-03-26 17:35:21 +0000
committercjhopman@chromium.org <cjhopman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-03-26 17:35:21 +0000
commitbd6ab3db3f2ac6f387eb1515e1db6ac9d3d9d0fe (patch)
treeaf797fbe1c9072edf7dcb3588542bb449d57a276 /build/android/empty_proguard.flags
parent060847ecad23482812eee34ea38b86a2e0d4500a (diff)
downloadchromium_src-bd6ab3db3f2ac6f387eb1515e1db6ac9d3d9d0fe.zip
chromium_src-bd6ab3db3f2ac6f387eb1515e1db6ac9d3d9d0fe.tar.gz
chromium_src-bd6ab3db3f2ac6f387eb1515e1db6ac9d3d9d0fe.tar.bz2
Split apk-build.xml into 3 steps
In preparation for rewriting these actions in python, split apk-build.xml into smaller ant scripts. This should not change the functionality and mostly is just splitting the file and identifying the properties and defines required for each of the new files. Some of the configuration is moved out of ant and into gyp (i.e. the android_manifest_path is now gyp-configurable). Also, the ant scripts now use the correct basedir! That is, these ant scripts actually understand relative paths. To go along with this, resource_dir is the relative path to the resource directory (rather than a path relative to java_in_dir). BUG=158821 TBR=torne@chromium.org, brettw@chromium.org NOTRY=true Review URL: https://chromiumcodereview.appspot.com/12963009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@190712 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'build/android/empty_proguard.flags')
-rw-r--r--build/android/empty_proguard.flags1
1 files changed, 1 insertions, 0 deletions
diff --git a/build/android/empty_proguard.flags b/build/android/empty_proguard.flags
new file mode 100644
index 0000000..53484fe
--- /dev/null
+++ b/build/android/empty_proguard.flags
@@ -0,0 +1 @@
+# Used for apk targets that do not need proguard. See build/java_apk.gypi.