commit | 40c399732cb9e9c83c2810116f07a6ca0753378a | [log] [tgz] |
---|---|---|
author | Christoffer Quist Adamsen <christofferqa@google.com> | Mon Feb 22 13:20:51 2021 +0100 |
committer | Christoffer Quist Adamsen <christofferqa@google.com> | Mon Feb 22 13:21:00 2021 +0100 |
tree | f30870efc78ae1ef39f38814955f040b4147e8ff | |
parent | d81abe7412c6ec67408e91fa725ae62a862cf521 [diff] |
Allow missing classes in R8 mk builds Bug: 180878971 Bug: 72683872 Test: TARGET_PRODUCT=aosp_arm64 m -j core-oj Change-Id: I4e3d49d4d8aa7e373bae6710db57f503eb95fab1
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.