summaryrefslogtreecommitdiffstats
path: root/docs/html
diff options
context:
space:
mode:
authorRich Slogar <rslogar@google.com>2015-05-18 17:12:22 +0000
committerAndroid (Google) Code Review <android-gerrit@google.com>2015-05-18 17:12:23 +0000
commit4e793fba568950ee2b3758e1482006661430440e (patch)
tree68674ee50cb46df9323c798a41c8a458a4a4cf1f /docs/html
parent193841bebf6be4efa4e0c3a0e5e4a44ceef24f6e (diff)
parent4af26cbfa40471778a506d438ad6085d4f06db4d (diff)
downloadframeworks_base-4e793fba568950ee2b3758e1482006661430440e.zip
frameworks_base-4e793fba568950ee2b3758e1482006661430440e.tar.gz
frameworks_base-4e793fba568950ee2b3758e1482006661430440e.tar.bz2
Merge "docs: build-cmd-line-updates" into lmp-mr1-ub-docs
Diffstat (limited to 'docs/html')
-rw-r--r--docs/html/tools/building/building-cmdline.jd8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/html/tools/building/building-cmdline.jd b/docs/html/tools/building/building-cmdline.jd
index 33798a5..0e4c8b2 100644
--- a/docs/html/tools/building/building-cmdline.jd
+++ b/docs/html/tools/building/building-cmdline.jd
@@ -43,7 +43,7 @@ parent.link=index.html
<p>Whether you're building with the debug or release build type, you need to run
and build your module. This will create the .apk file that you can install on an emulator or device.
When you build using the debug build type, the .apk file is automatically signed by the SDK tools
- with a debug key based on the <code>debuggable true</code> setting in the module's gradle.build file,
+ with a debug key based on the <code>debuggable true</code> setting in the module's build.gradle file,
so it's instantly ready for installation onto an emulator or attached
development device. You cannot distribute an application that is signed with a debug key.
When you build using the release build type, the .apk file is <em>unsigned</em>, so you
@@ -174,7 +174,7 @@ $ ./gradlew assembleRelease
the build will prompt you for your keystore and alias password when you build using the release
build type and produce your final application package, which will be ready for distribution.</p>
- <p>To specify your keystore and alias, open the module gradle.build file (found in
+ <p>To specify your keystore and alias, open the module build.gradle file (found in
the root of the module directory) and add entries for {@code storeFile}, {@code storePassword},
{@code keyAlias} and {@code keyPassword}.
For example:</p>
@@ -188,7 +188,7 @@ keyAlias "MyReleaseKey"
<ol>
<li>Open a command-line and navigate to the root of your module directory.</li>
- <li>Edit the gradle.build file to build your project in release mode:
+ <li>Edit the build.gradle file to build your project in release mode:
<p><pre>
...
android {
@@ -222,7 +222,7 @@ android {
<p>This creates your Android application .apk file inside the module <code>build/</code>
directory, named <code><em>&lt;your_module_name&gt;</em>-release.apk</code>. This .apk file has
- been signed with the private key specified in gradle.build file and aligned with {@code
+ been signed with the private key specified in build.gradle file and aligned with {@code
zipalign}. It's ready for installation and distribution.</p>
<h3 id="OnceBuilt">Once built and signed in release mode</h3>