commit | eda150c3ebc64edfd2dd1dd12573304e8a5d362a | [log] [tgz] |
---|---|---|
author | Cory Barker <cobark@google.com> | Mon Aug 08 16:47:05 2022 +0000 |
committer | Cory Barker <cobark@google.com> | Mon Aug 08 19:12:02 2022 +0000 |
tree | 2b2128a37089b5cfc10d026c7b4dcafab11de1e5 | |
parent | 85125778f571e6e626c7f7de71a847a2b40bf25c [diff] |
Revert^2 "Updated the way we build AFL++ fuzz binaries" f3486b10201c7c5588846f5e7fa704ceabf962ce Change-Id: Ib81aa706f5f9984b44ffaee7ccafba1728b55e6d
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.