| commit | b44af1747c82c273cb360fd6ca85febae3e34ae5 | [log] [tgz] |
|---|---|---|
| author | Luca Farsi <lucafarsi@google.com> | Mon Nov 18 11:59:43 2024 -0800 |
| committer | Luca Farsi <lucafarsi@google.com> | Mon Nov 18 13:57:36 2024 -0800 |
| tree | 37e5368cc37df94830d9105e6ef1278550b9d99b | |
| parent | 5e393bc8c4a656c468621ff7fc793ed3e7b9d8e4 [diff] |
Report optimized/unoptimized targets correctly Always report every target that gets built as unoptimized, and only report targets that wouldn't get built as optimized. Previously when test discovery succeeded only targets that get built were getting reported (as optimized when those were the unoptimized ones), and targets that wouldn't get built were not being reported at all (when those would be the optimized targets). Test: Presubmit Bug: 372973116 Change-Id: I0b22b57654bba90d9eb398651b09ae0f65df0d5c
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.