| commit | 05d007ae203ee40e9f132b303e7e195b1febcb77 | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Thu Aug 26 05:26:46 2021 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Aug 26 05:26:46 2021 +0000 |
| tree | d83fbfd390c70cd283fe599b76d19f0910a72160 | |
| parent | a44660f3a625702bcc47657218629a095a6c8be9 [diff] | |
| parent | ee20ae1a8dcdfe7b843d65099000708800d9b93a [diff] |
Merge "Propagate USE_HOST_MUSL to Soong" am: ee20ae1a8d Original change: https://android-review.googlesource.com/c/platform/build/+/1796674 Change-Id: Ie9c9e6ed81a70d699537131a5cd9d77c3f8eca7b
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.