| commit | e37e24906ad1ba76e1ee9a2fbcae4a3434b346b4 | [log] [tgz] |
|---|---|---|
| author | Tom Marshall <tdm@cyngn.com> | Tue Nov 07 21:44:11 2017 -0500 |
| committer | Aren Clegg <compiterman2k3@live.com> | Sat Aug 25 00:35:36 2018 +0000 |
| tree | 83388929b8390d4d3809cfecae6a71550e766d75 | |
| parent | 311cb82cc182d8a412395adf415165f275373240 [diff] |
Support for install tools in /tmp/install * Anything in OUT/install gets packaged up into the zip and extracted to /tmp/install immediately after FullOTA_InstallBegin. * Use /tmp/install in edify scripts and remove code related to using and manipulating /system for install tools. Change-Id: Ia55403ad78a2be7030a4cc5fba15f35295d5beaf
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.