| commit | aca50a088fa0d76719f000bfabad6661156a1f83 | [log] [tgz] |
|---|---|---|
| author | Abhishek Nigam <abhisheknigam@google.com> | Thu Nov 09 02:44:06 2023 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Nov 09 02:44:06 2023 +0000 |
| tree | c69532df9146e8beb49c21259e5062097787222f | |
| parent | 34e4532a2f41b9d9f7c326cf951e6a03c38a1b03 [diff] | |
| parent | 0f6414aa4a05560cc2b073d09d1c1eb3ad674239 [diff] |
Merge changes from topic "nonabrevert" into main am: 80b1a3fc38 am: 795ffffd00 am: 0f6414aa4a Original change: https://android-review.googlesource.com/c/platform/build/+/2820713 Change-Id: Iadd235d2910f6105da97bf78782bcd63041c6424 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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.