commit | 94e579b9a34c05f41d1aa046158ad4df67b2393c | [log] [tgz] |
---|---|---|
author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Feb 03 19:33:30 2020 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Feb 03 19:33:30 2020 +0000 |
tree | 6db27e06e525863b495fcc887fca67605ea30887 | |
parent | 123c1e9a20b58dced03847bfc387abc5ed1f60b2 [diff] | |
parent | 910347f464376867c298fa7dfd961cc56e464692 [diff] |
[automerger skipped] Modify build to put dumpcoverage agent into /system/lib am: 3ed9021f87 am: 910347f464 -s ours am skip reason: Change-Id Ib2fece1b41a3b5d16c8a2a444c5486137e475fda with SHA-1 7185f8cc2d is in history Change-Id: Ic1bdb4f56d84a8e4d2a74d485120ed6a835b0279
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.