diff options
Diffstat (limited to 'docs/html/tools/building')
| -rw-r--r-- | docs/html/tools/building/building-cmdline.jd | 17 | ||||
| -rw-r--r-- | docs/html/tools/building/building-studio.jd | 19 | ||||
| -rw-r--r-- | docs/html/tools/building/configuring-gradle.jd | 8 | ||||
| -rw-r--r-- | docs/html/tools/building/plugin-for-gradle.jd | 13 |
4 files changed, 21 insertions, 36 deletions
diff --git a/docs/html/tools/building/building-cmdline.jd b/docs/html/tools/building/building-cmdline.jd index ec00b50..33798a5 100644 --- a/docs/html/tools/building/building-cmdline.jd +++ b/docs/html/tools/building/building-cmdline.jd @@ -34,9 +34,9 @@ parent.link=index.html </div> </div> - <p>By default, there are two build types to build your application using the gradle.build settings: + <p>By default, there are two build types to build your application using the Gradle build settings: one for debugging your application — <em>debug</em> — and one for building your - final package for release — <em>release mode</em>. Regardless of which way you build type + final package for release — <em>release mode</em>. Regardless of which build type your modules use, the app must be signed before it can install on an emulator or device—with a debug key when building in debug mode and with your own private key when building in release mode.</p> @@ -48,23 +48,24 @@ parent.link=index.html 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 must manually sign it with your own private key, using Keytool and Jarsigner settings in the - module's gradle.build file.</p> + module's <code>build.gradle</code> file.</p> <p>It's important that you read and understand <a href= "{@docRoot}tools/publishing/app-signing.html">Signing Your Applications</a>, particularly once you're ready to release your application and share it with end-users. That document describes the - procedure for generating a private key and then using it to sign your .apk file. If you're just + procedure for generating a private key and then using it to sign your APK file. If you're just getting started, however, you can quickly run your applications on an emulator or your own development device by building in debug mode.</p> <p>If you don't have <a href="http://www.gradle.org/">Gradle</a>, you can obtain it from the <a href="http://gradle.org/">Gradle - home page</a>. Install it and make sure it is in your executable PATH. Before calling Ant, you + home page</a>. Install it and make sure it is in your executable PATH. Before calling Gradle, you need to declare the JAVA_HOME environment variable to specify the path to where the JDK is installed.</p> - <p class="note"><strong>Note:</strong> When installing JDK on Windows, the default is to install - in the "Program Files" directory. This location will cause <code>ant</code> to fail, because of - the space. To fix the problem, you can specify the JAVA_HOME variable like this: + <p class="note"><strong>Note:</strong> When using <code>ant</code> and installing JDK on Windows, + the default is to install in the "Program Files" directory. This location will cause + <code>ant</code> to fail, because of the space. To fix the problem, you can specify the JAVA_HOME + variable like this: <pre>set JAVA_HOME=c:\Progra~1\Java\<jdkdir></pre> <p>The easiest solution, however, is to install JDK in a non-space directory, for example:</p> diff --git a/docs/html/tools/building/building-studio.jd b/docs/html/tools/building/building-studio.jd index 68800da..4431194 100644 --- a/docs/html/tools/building/building-studio.jd +++ b/docs/html/tools/building/building-studio.jd @@ -67,26 +67,13 @@ selected build variant. For more information, see the <a href="{@docRoot}sdk/installing/studio-build.html">Build System</a> guide.</p> <p>To view the list of all available build tasks in Android Studio, click <strong>Gradle</strong> -on the right side of the IDE window. The <em>Gradle tasks</em> panel appears as shown in -figure 2. Double-click any build task to run it in Android Studio. To hide the <em>Gradle tasks</em> -panel, click <strong>Gradle</strong> again.</p> +on the right side of the IDE window. The <em>Gradle tasks</em> panel appears.</p> -<img src="{@docRoot}images/tools/studio-gradle-panel.png" alt="" /> -<p class="img-caption"><strong>Figure 2.</strong> The list of build tasks in Android Studio.</p> <h3 id="buildRelease">Build a release version</h3> -<p>You can now build the release version of your application for distribution. To build it from Android -Studio:</p> - -<ol> - <li>Click <strong>Gradle</strong> on the right side of the IDE window.</li> - <li>On the <em>All tasks</em> section of the sidebar that appears, expand - <strong>BuildSystemExample</strong>.</li> - <li>Expand <strong>:app</strong> and double-click <strong>assembleRelease</strong>.</li> -</ol> - -<p>You can use this procedure to invoke any build task from Android Studio.</p> +<p>You can now use the <strong>Build</strong> menu options to build the release version of your +application for distribution. </p> <p>The build generates an APK for each build variant: the <code>app/build/apk/</code> directory contains packages named diff --git a/docs/html/tools/building/configuring-gradle.jd b/docs/html/tools/building/configuring-gradle.jd index 8379508..7cca5b4 100644 --- a/docs/html/tools/building/configuring-gradle.jd +++ b/docs/html/tools/building/configuring-gradle.jd @@ -470,7 +470,11 @@ applied to each build. </p> <li>fullRelease</li> </ul> -<p>To build this example, invoke the <code>assemble</code> task from Android Studio or from the -command line.</p> +<p>To build this example, click the <strong>Build</strong> menu option in Android Studio or invoke +the <code>assemble</code> task from the command line. </p> + +<p class="note"><strong>Note:</strong> The <strong>Build > Make Project</strong> option compiles +all the source files in the entire project that have been modified since the last compilation. The +<strong>Build > Rebuild Project</strong> option recomplies all the source files in the project.</p> <p>Separate output folders are created for each build variant. </p> diff --git a/docs/html/tools/building/plugin-for-gradle.jd b/docs/html/tools/building/plugin-for-gradle.jd index 54a03fd..a497c1b 100644 --- a/docs/html/tools/building/plugin-for-gradle.jd +++ b/docs/html/tools/building/plugin-for-gradle.jd @@ -15,7 +15,7 @@ page.title=Android Plug-in for Gradle <li><a href="{@docRoot}sdk/installing/studio-build.html"> Build System Overview</a></li> <li><a href="{@docRoot}tools/building/index.html"> -Buidling and Running</a></li> +Building and Running</a></li> <li><a href="{@docRoot}tools/building/building-studio.html"> Building and Running from Android Studio</a></li> </ul> @@ -273,16 +273,9 @@ tasks are:</p> <dd><p>Performs the clean.</p></dd> </dl> -<p>The Android plugin provides additional tasks for <em>connectedCheck</em> and <em>deviceCheck</em> +<p>The Android plugin provides the <em>connectedCheck</em> and <em>deviceCheck</em> tasks for checks run on connected, emulated, and remote devices. Gradle tasks can be viewed by clicking -the Gradle tab</a> in the right margin. -<img src="{@docRoot}images/tools/studio-gradle-tab.png"></p> -<p class="img-caption"><strong>Figure 1:</strong> Gradle tab</p> - -<p>Running a top-level task, runs all the dependent tasks. For example, the <em>assemble</em> task -has dependent tasks for <em>assembleDebug</em> and <em>assembleRelease</em> to make the debug and -release APKs. The <em>assemble</em> task depends on these tasks so calling it builds both APKs. -These tasks can also be called independently to build the debug or release APK separately. </p> +the Gradle tab</a> in the right margin.</p> <p>You can view the list of available tasks and invoke any task from Android Studio and from the command line, as described in |