| commit | 8f8615329da91d3776a052965098249ded42d525 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Tue Jul 24 12:05:47 2018 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Tue Jul 24 12:05:47 2018 -0700 |
| tree | 7f425f5eb2b4828a5ca4c04e8f24b997e9258f6b | |
| parent | 59af365c9b61d6e0b968d1d418cd765787dcc1ce [diff] | |
| parent | 7e1a715b7655677faad10df0d7e37f75bd5c7ecb [diff] |
Merge "releasetools: Support verifying AVB signed images with chained partitions." am: 78078646e9 am: fdcb3b5829 am: 64cc19ca7e am: 7e1a715b76 Change-Id: I9c577ca051ce5cc44a109feb5a1d721bac78ab2f
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.