| commit | a49b0c8613b57cd07b82476a8934faa3e14227a9 | [log] [tgz] |
|---|---|---|
| author | Steve Muckle <smuckle@google.com> | Sun Aug 09 15:24:54 2020 -0700 |
| committer | Steve Muckle <smuckle@google.com> | Sun Aug 09 18:11:56 2020 -0700 |
| tree | 72898779c5ad8c1484722ffa2af9f1c9325dbee5 | |
| parent | a21b44a736ea99e2ad0e2079038c21bf58afbabb [diff] |
add BOARD_GKI_NONAB_COMPAT for non-A/B compatability with GKI The directory structure of several ramdisks are different depending on whether the target is A/B or non-A/B. When the target needs to be compatible with the GKI however, which is always built as A/B, it is necessary to build these ramdisks using the A/B file hierarchy. Provide a flag to enable this override when necessary. Bug: 161579556 Change-Id: I1cf9a0ef5a338b0b5152113533b62804f3088c83
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.