commit | 8046cb0a2c3112a4d3abd59bbe54bad9150ded2b | [log] [tgz] |
---|---|---|
author | Oleg Aravin <erkfel@google.com> | Tue Jun 02 16:02:38 2020 -0700 |
committer | Oleg Aravin <erkfel@google.com> | Tue Jun 02 16:03:21 2020 -0700 |
tree | 3d49710b1d7b5622ce748ce9a4d0c4f3a4c09f6a | |
parent | fa9ea4b8b03cfc4baf0f056e750749540ad219f3 [diff] |
Attach apk_name as a suffix for the temporary files With this change the name of the signed and unsigned APK will be something like 'tmpadrbpp9f/tmpvl0lf2kr/tmpknja6mca_MyApk.apk' instead of 'tmpadrbpp9f/tmpvl0lf2kr/tmpknja6mca'. The motivation for this change is a better logging and transparency what is being signed in the underlying client. Change-Id: I32b0e93d5859ca3fb712e426705f16d329d71f0e
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.