| commit | 934bd8dcfcc9de8de015dd49c317456b16279a0f | [log] [tgz] |
|---|---|---|
| author | Joe Onorato <joeo@google.com> | Thu Jul 16 18:10:48 2020 -0700 |
| committer | Joe Onorato <joeo@google.com> | Thu Sep 10 14:09:28 2020 -0700 |
| tree | 0aa86fd35095abe4c3d271673c832744e07aff3e | |
| parent | a51b1b857bc4581d11f10ba35692eadcaf80ab7d [diff] |
Add per-partition summaries and "easy" transitions to mk2bp_catalog "Easy" means makefiles that are both clean themselves and only depend on clean targets themselves too. Test: m out/target/product/$(get_build_var TARGET_DEVICE)/mk2bp_remaining.html Change-Id: If3402a0ada5d9db5fb04c617d197ab28d695b03c
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.