| commit | 259894a559b89576e1885cc5b8558f372c3b66f2 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Mon Sep 23 07:45:38 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Mon Sep 23 07:45:38 2019 -0700 |
| tree | a1855a43a3d98525777aec3e37e33bb7994177ac | |
| parent | a91f8768a1b288fffdc9da982597972f86fec13f [diff] | |
| parent | 8e57ab97e16a514e10c80723524dd412233d9c6c [diff] |
Merge "Don't generate hashtree when signing bundled APEXes." am: 08f9da1898 am: 8f7e2e8eaa am: 8e57ab97e1 Change-Id: Ic61159d2ec53930e6d80154aa084e4a70c588efa
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.