From b89a4766271a8306c255fd70864650683b54e4a6 Mon Sep 17 00:00:00 2001 From: agrieve Date: Fri, 15 Jan 2016 09:42:10 -0800 Subject: Don't use chrome_apk_version_code in remoting_apk. chrome_apk_version_code is for chrome_apk. There are now global args for setting the default version code & name for targets that don't want to create their own: - android_default_version_name - android_default_version_code BUG=none Review URL: https://codereview.chromium.org/1589243002 Cr-Commit-Position: refs/heads/master@{#369782} --- remoting/android/remoting_apk_tmpl.gni | 3 --- 1 file changed, 3 deletions(-) (limited to 'remoting/android') diff --git a/remoting/android/remoting_apk_tmpl.gni b/remoting/android/remoting_apk_tmpl.gni index 57d5e57..bc440c3 100644 --- a/remoting/android/remoting_apk_tmpl.gni +++ b/remoting/android/remoting_apk_tmpl.gni @@ -3,15 +3,12 @@ # found in the LICENSE file. import("//build/config/android/rules.gni") -import("//chrome/android/chrome_apk_version.gni") if (!is_component_build) { template("remoting_apk_tmpl") { android_apk(target_name) { forward_variables_from(invoker, "*") - version_name = chrome_apk_version_name - version_code = chrome_apk_version_code android_manifest = "$root_gen_dir/remoting/android/AndroidManifest.xml" native_libs = [ "libremoting_client_jni.so" ] -- cgit v1.1