* 转载请注明出处
* 所有资料整理均为网络资源信息搜索所得
> Android-NDK 下载地址列表
> Android-SDK-Tools only
V Android-Studio
V Android-构建过程描述
* build
* The general process for a typical build is outlined below. The build system merges all the resources from the configured product flavors, build types, and dependencies. If different folders contain resources with the same name or setting, the following override priority order is: dependencies override build types, which override product flavors, which override the main source directory.
* The Android Asset Packaging Tool (aapt) takes your application resource files, such as the AndroidManifest.xml file and the XML files for your Activities, and compiles them. An is also produced so you can reference your resources from your Java code.
* The aidl tool converts any .aidl interfaces that you have into Java interfaces.
* All of your Java code, including the and .aidl files, are compiled by the Java compiler and .class files are output.
* The dex tool converts the .class files to Dalvik byte code. Any 3rd party libraries and .class files that you have included in your module build are also converted into .dex files so that they can be packaged into the final .apk file.
* All non-compiled resources (such as images), compiled resources, and the .dex files are sent to the apkbuilder tool to be packaged into an .apk file.
* Once the .apk is built, it must be signed with either a debug or release key before it can be installed to a device.
* Finally, if the application is being signed in release mode, you must align the .apk with the zipalign tool. Aligning the final .apk decreases memory usage when the application is -running on a device.