| commit | 8a49a601434552404b94f91af751a29748dd072f | [log] [tgz] |
|---|---|---|
| author | Cory Barker <cobark@google.com> | Fri Jul 22 17:33:36 2022 +0000 |
| committer | Cory Barker <cobark@google.com> | Tue Aug 02 02:23:23 2022 +0000 |
| tree | 782ec99a27d8b8f547a4b3e6d10f3e4e50c37c7b | |
| parent | 1fabb2a942060fe6b6082cb0f00e287e97172a78 [diff] |
Updated the way we build AFL++ fuzz binaries Test: Built AFL fuzzers individually and built all using haiku command and built libfuzzers individually and also by using haiku command. Ran selected fuzzers manually to ensure fuzzing still worked. Description: Previously we needed to add cc_afl_fuzz to build an afl fuzz binary, however, to turn current libFuzzers into AFL fuzzers this would required an update to each Android.bp file which is a lot of work, and would also require an approval from each Android.bp file owner, which is even more work. To get around this (and also to match how AFL fuzzers are built in G3) we will build AFL++ fuzz binaries by command line option FUZZ_FRAMEWORK. When FUZZ_FRAMEWORK=AFL is set, all cc_fuzz modules will be built Change-Id: I994bde63b759046c9e3d75d3acfdc1352412005b
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.