| commit | 4c9153bae082c6ee859d36390bfd99b347916683 | [log] [tgz] |
|---|---|---|
| author | Omar Eissa <oeissa@google.com> | Fri Apr 28 14:43:34 2023 +0000 |
| committer | Omar Eissa <oeissa@google.com> | Fri Apr 28 14:57:03 2023 +0000 |
| tree | a25d7dc9e7d85884807dc732647e2f91071a4188 | |
| parent | 6871bbf91ea92e86d82fcc2d56f2c8b89a06d670 [diff] |
Exclude apps from initial stopped state allow list Exclude apps that we have high confidence that force stopping them wouldn't be an issue given that they don't need to start until the user interacts with them. Bug: 269129704 Test: Manual Ignore-AOSP-First: Merge conflict from AOSP to internal master (and this needs to go to UDC, als) Change-Id: I363fbd4d899aed6772199b05fa763be3fa5f31b6
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.