| commit | 72eed42550ed1507f73332c175691416eb92a373 | [log] [tgz] |
|---|---|---|
| author | Treehugger Robot <treehugger-gerrit@google.com> | Mon Apr 05 05:52:47 2021 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Apr 05 05:52:47 2021 +0000 |
| tree | a848d0a27d67a811430b8d53bcf313f525721f92 | |
| parent | dd1ee0b78f3ca8c5bb621fa479c799a8ad26d457 [diff] | |
| parent | 79c96bf3a95135863f8d436133ffe80b0c495b18 [diff] |
Merge "Generate care map after merging target_files" am: f92961248b am: 79c96bf3a9 Original change: https://android-review.googlesource.com/c/platform/build/+/1649488 Change-Id: I2b00b86b6730fefc2408bf0131ef6e752826f76b
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.