| commit | 2177290e8288923d8292ac03275ccdff1a558de6 | [log] [tgz] |
|---|---|---|
| author | android-build-team Robot <android-build-team-robot@google.com> | Fri Jun 19 07:06:31 2020 +0000 |
| committer | android-build-team Robot <android-build-team-robot@google.com> | Fri Jun 19 07:06:31 2020 +0000 |
| tree | 3573cd68cecd38b3d4ca3ed596fae054625d9da4 | |
| parent | 2e82793229e0286f9f53747a17f41af3963f17b8 [diff] | |
| parent | 5f051428b018b2e2afdfc7d6bd0a04754cd5b886 [diff] |
Snap for 6607158 from 5f051428b018b2e2afdfc7d6bd0a04754cd5b886 to mainline-release Change-Id: I4dc1c35a2b9f1671b06b06b7a9e6e30e0def6987
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.