commit | 61a792f323e2a42baa7692540aa57036f8426b56 | [log] [tgz] |
---|---|---|
author | Tianjie Xu <xunchang@google.com> | Tue Jan 28 10:54:50 2020 -0800 |
committer | Tianjie Xu <xunchang@google.com> | Tue Jan 28 10:58:14 2020 -0800 |
tree | 1db27abab53d737d105354a2bf6d80ac730e351e | |
parent | 62f97c7fb46e268e4d35fddb7fd9cdebacd2e55d [diff] |
Make the error more instructive on missing android_jar_path So when $ANDROID_BUILD_TOP is missing, the error message print out the path of the missing file; instead of a type error. Bug: 148452817 Test: check result with missing ANDROID_BUILD_TOP Change-Id: I5f841f6626eb3843364f20e78b278d3244505396
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.