| commit | 3ab7e011477c601f3ccf52f50cf1a6b4de75a81b | [log] [tgz] |
|---|---|---|
| author | Dennis Shen <dzshen@google.com> | Thu Apr 11 20:59:54 2024 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Apr 11 20:59:54 2024 +0000 |
| tree | acff7aee84f9d8fb7d0618f7cf975812ff6338a3 | |
| parent | 736f1e23fad5a851aac0d0c8b332c8962ca134b7 [diff] | |
| parent | c54746ed3149f0196d7e2261361ae5a788cc19e9 [diff] |
Merge changes from topic "flag_info_write" into main am: 82546539f1 am: c54746ed31 Original change: https://android-review.googlesource.com/c/platform/build/+/3034972 Change-Id: I87da3e3229c176eddc9f3947ef5e43ca8e3aff84 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.