Remove anomaly detector double flagging. The anomaly detector code is already feature-flagged by the “android.os.profiling.anomaly.flags.anomaly_detector_core” aconfig flag. An additional build flag was introduced for the following two reasons: - Our code is inside the Profiling module and we wanted to avoid shipping it in the initial phase; - We wanted to avoid potential coverage drops in the mainline module due to the addition of new code. These two justifications are no longer valid. “Profiling” won’t ship a new version until 26Q2 (when we are releasing our code) and the coverage infrastructure is not smart enough to automatically exclude code based on a build flag. We have additionally verified that our code coverage meets the mainline module target. This “double flagging” is causing several issues, especially when they go out of sync. This feature as a whole should only be behind a single flag. Bug: 470415713 Test: atest CtsAnomalyDetectorTests Test: atest MtsAnomalyDetectorTests Flag: EXEMPT HOST_MODE Change-Id: I458e3dce628a3295ed045dfbca8d66f841ff3f3a
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.