android命令行编译生成apk(翻译官方文档)

英文文档来源于官方文档,鉴于英文学习目的和很多同学访问不了该站点，在这里http://developer.android.com/tools/building/building-cmdline.html

By default, there are two build types to build your application using the gradle.build settings: one for

通常,使用gradle.build settings编译你的应用程序有以下两种编译类型:

debugging your application —debug— and one for building your final package for release

一个debug模式：调试你的应用，另外一个是发布模式：编译成最终的发布应用。

—release mode. Regardless of which way you build type your modules use, the app must be signed

不论你使用哪种方式编译你的模块，app运行在设备或者模拟器之前都需要被签名。

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.

在debug模式使用一个debug key,在发布模式使用一个你的私有key进行编译。

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

这时将会生成一个以.apk结尾的文件,然后你可以在模拟器或者真机上安装它。

debug build type, the .apk file is automatically signed by the SDK tools with a debug key based on

在使用调试模式时,如果gradle.build文件中debuggable=true时,apk文件是自动使用sdk 工具包里面自带的debug key签名。

thedebuggable truesetting in the module's gradle.build file, so it's instantly ready for installation onto

所以apk文件可以成功安装在模拟器或者开发设备商。

an emulator or attached development device. You cannot distribute an application that is signed

你不要分发你的使用debug key签名的应用程序.

with a debug key. When you build using the release build type, the .apk file isunsigned, so you must

当你用发布模拟编译时,apk文件是没有被签名的,你必须使用你的私有key用keytool和jarsigner签名。这些都在gradle.build文件。

manually sign it with your own private key, using Keytool and Jarsigner settings in the module's gradle.build file.

It's important that you read and understandSigning Your Applications, particularly once you're

其他不明白的可以看signing Your Applications.

readygengx

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 getting started, however, you can quickly run your applications on an emulator or your own development device by building in debug mode.

If you don't haveGradle, you can obtain it from theGradle home page. Install it and make sure it is in your executable PATH. Before calling Ant, you need to declare the JAVA_HOME environment variable to specify the path to where the JDK is installed.

Note:When installing JDK on Windows, the default is to install in the "Program Files" directory. This location will causeantto fail, because of the space. To fix the problem, you can specify the JAVA_HOME variable like this:

set JAVA_HOME=c:\Progra~1\Java\<jdkdir>

The easiest solution, however, is to install JDK in a non-space directory, for example:

c:\java\jdk1.7

Building in Debug Mode

For immediate application testing and debugging, you can build your application in debug mode and immediately install it on an emulator. In debug mode, the build tools automatically sign your application with a debug key and optimize the package withzipalign.

To build in debug mode, open a command-line and navigate to the root of your project directory. Use Gradle to build your project in debug mode, invoke theassembleDebugbuild task using the Gradle wrapper script (gradlew assembleRelease).

This creates your debug.apkfile inside the modulebuild/directory, named<your_module_name>-debug.apk. The file is already signed with the debug key and has been aligned withzipalign.

On Windows platforms, type this command:

> gradlew.bat assembleDebug

On Mac OS and Linux platforms, type these commands:

$ chmod +x gradlew$ ./gradlew assembleDebug

The first command (chmod) adds the execution permission to the Gradle wrapper script and is only necessary the first time you build this project from the command line.

After you build the project, the output APK for the app module is located inapp/build/outputs/apk/, and the output AAR for any lib modules is located inlib/build/outputs/libs/.

To see a list of all available build tasks for your project, type this command:

$ ./gradlew tasks

Each time you change a source file or resource, you must run Gradle again in order to package up the latest version of the application.

To install and run your application on an emulator, see the section aboutRunning on the Emulator.

Building in Release Mode

When you're ready to release and distribute your application to end-users, you must build your application in release mode. Once you have built in release mode, it's a good idea to perform additional testing and debugging with the final .apk.

Before you start building your application in release mode, be aware that you must sign the resulting application package with your private key, and should then align it using thezipaligntool. There are two approaches to building in release mode: build an unsigned package in release mode and then manually sign and align the package, or allow the build script to sign and align the package for you.

Build unsigned

If you build your applicationunsigned, then you will need to manually sign and align the package.

To build anunsigned.apk in release mode, open a command-line and navigate to the root of your module directory. Invoke theassembleReleasebuild task.

On Windows platforms, type this command:

> gradlew.bat assembleRelease

On Mac OS and Linux platforms, type this command:

$ ./gradlew assembleRelease

This creates your Android application .apk file inside the projectbin/directory, named<your_module_name>-unsigned.apk.

Note:The .apk file isunsignedat this point and can't be installed until signed with your private key.

Once you have created the unsigned .apk, your next step is to sign the .apk with your private key and then align it withzipalign. To complete this procedure, readSigning Your Applications.

When your.apkhas been signed and aligned, it's ready to be distributed to end-users. You should test the final build on different devices or AVDs to ensure that it runs properly on different platforms.

Build signed and aligned

If you would like, you can configure the Android build script to automatically sign and align your application package. To do so, you must provide the path to your keystore and the name of your key alias in your modules's build.gradle file. With this information provided, 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.

To specify your keystore and alias, open the module gradle.build file (found in the root of the module directory) and add entries forstoreFile,storePassword,keyAliasandkeyPassword. For example:

storeFile file("myreleasekey.keystore")keyAlias "MyReleaseKey"

Save your changes. Now you can build asigned.apk in release mode:

Open a command-line and navigate to the root of your module directory.

Edit the gradle.build file to build your project in release mode:

...android {  ...  defaultConfig { ... }  signingConfigs {    release {      storeFile file("myreleasekey.keystore")      storePassword "password"      keyAlias "MyReleaseKey"      keyPassword "password"    }  }  buildTypes {    release {      ...      signingConfig signingConfigs.release    }  }}...

When prompted, enter you keystore and alias passwords.
Caution:As described above, your password will be visible on the screen.

This creates your Android application .apk file inside the modulebuild/directory, named<your_module_name>-release.apk. This .apk file has been signed with the private key specified in gradle.build file and aligned withzipalign. It's ready for installation and distribution.

Once built and signed in release mode

Once you have signed your application with a private key, you can install and run it on anemulatorordevice. You can also try installing it onto a device from a web server. Simply upload the signed .apk to a web site, then load the .apk URL in your Android web browser to download the application and begin installation. (On your device, be sure you have enabledSettings > Applications > Unknown sources.)

Running on the Emulator

Before you can run your application on the Android Emulator, you mustcreate an AVD.

To run your application:

Open the AVD Manager and launch a virtual device
From your SDK'splatform-tools/directory, execute theandroidtool with theavdoptions:
```
android avd
```
In theVirtual Devicesview, select an AVD and clickStart.
Install your application
From your SDK'stools/directory, install the.apkon the emulator:
```
adb install <path_to_your_bin>.apk
```
Your .apk file (signed with either a release or debug key) is in your modulebuild/directory after you build your application.

If there is more than one emulator running, you must specify the emulator upon which to install the application, by its serial number, with the-soption. For example:
```
adb -s emulator-5554 install path/to/your/app.apk
```
To see a list of available device serial numbers, executeadb devices.

If you don't see your application on the emulator, try closing the emulator and launching the virtual device again from the AVD Manager. Sometimes when you install an application for the first time, it won't show up in the application launcher or be accessible by other applications. This is because the package manager usually examines manifests completely only on emulator startup.

Be certain to create multiple AVDs upon which to test your application. You should have one AVD for each platform and screen type with which your application is compatible. For instance, if your application compiles against the Android 4.0 (API Level 14) platform, you should create an AVD for each platform equal to and greater than 4.0 and an AVD for eachscreen typeyou support, then test your application on each one.

Tip:If you haveonly oneemulator running, you can build your application and install it on the emulator in one simple step. Navigate to the root of your project directory and use Ant to compile the project withinstall mode:ant install. This will build your application, sign it with the debug key, and install it on the currently running emulator.

Running on a Device

Before you can run your application on a device, you must perform some basic setup for your device:

EnableUSB debuggingon your device.
- On most devices running Android 3.2 or older, you can find the option underSettings > Applications > Development.
- On Android 4.0 and newer, it's inSettings > Developer options.
  Note:On Android 4.2 and newer,Developer optionsis hidden by default. To make it available, go toSettings > About phoneand tapBuild numberseven times. Return to the previous screen to findDeveloper options.
Ensure that your development computer can detect your device when connected via USB

ReadSetting up a Device for Developmentfor more information.

Once your device is set up and connected via USB, navigate to your SDK'splatform-tools/directory and install the.apkon the device:

adb -d install path/to/your/app.apk

The-dflag specifies that you want to use the attached device (in case you also have an emulator running).

For more information on the tools used above, please see the following documents:

android Tool
Android Emulator
Android Debug Bridge(ADB)

Application Signing

As you begin developing Android applications, understand that all Android applications must be digitally signed before the system will install them on an emulator or device. There are two ways to do this: with adebug key(for immediate testing on an emulator or development device) or with aprivate key(for application distribution).

The Android build tools help you get started by automatically signing your .apk files with a debug key at build time. This means that you can build your application and install it on the emulator without having to generate your own private key. However, please note that if you intend to publish your application, youmustsign the application with your own private key, rather than the debug key generated by the SDK tools.

Android Studio helps you get started quickly by signing your .apk files with a debug key, prior to installing them on an emulator or development device. This means that you can quickly run your application from Android Studio without having to generate your own private key. No specific action on your part is needed, provided ADT has access to Keytool. However, please note that if you intend to publish your application, youmustsign the application with your own private key, rather than the debug key generated by the SDK tools.

Please readSigning Your Applications, which provides a thorough guide to application signing on Android and what it means to you as an Android application developer. The document also includes a guide to publishing and signing your application.

Android Plugin for Gradle

The Android build system uses the Android plugin for Gradle to support the Gradle Domain Specific Language (DSL) and declarative language elements. See theAndroid Plug-in for Gradlesection for a description of the plugin and a link to the complete list of the supported Gradle DSL elements.