| commit | 96b0c0d9d7dd65d36461be3920832d4f9e410be9 | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Tue Mar 20 13:36:40 2018 -0700 |
| committer | Colin Cross <ccross@android.com> | Tue Mar 20 15:44:43 2018 -0700 |
| tree | c1584d2fbb3da9382318579ba0066027de1a4ecd | |
| parent | f6d68cf6fe4918880704dc3e0ebdeefa0f655162 [diff] |
Add asan-specific CleanSpec ASAN builds run as two consecutive builds. The cleanspec is applied by the first one, which cleans the obj directory, and ignored by the second. This can result in old entries in the obj_asan directory. Test: obj_asan dirs are deleted Change-Id: I54b8ec9cff581fcd9ec2a843aa7126805340c387 Merged-In: I54b8ec9cff581fcd9ec2a843aa7126805340c387 (cherry picked from commit 4e2da3277a1297bd403b07abcf9a36275826424b)
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.