| commit | 687e845c10b23c9d83074e0956aed03f8184b1f9 | [log] [tgz] |
|---|---|---|
| author | android-build-team Robot <android-build-team-robot@google.com> | Tue Jul 09 03:07:11 2019 +0000 |
| committer | android-build-team Robot <android-build-team-robot@google.com> | Tue Jul 09 03:07:11 2019 +0000 |
| tree | a34b6437ef7465ed1704fc276c7712166a178747 | |
| parent | fd33eac3ed34779c7b13cc31f0d8618109139744 [diff] | |
| parent | 25065c44ccce11172ad769f9f7b52aa3938109cb [diff] |
Snap for 5713174 from 25065c44ccce11172ad769f9f7b52aa3938109cb to qt-aml-release Change-Id: I50e4383a10278fd78dd39dd919857298db48545b
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.