| commit | 1008b3e89dc1def5a8c0261d3c8786feeeb8a248 | [log] [tgz] |
|---|---|---|
| author | Atneya Nair <atneya@google.com> | Wed Nov 06 11:40:53 2024 -0800 |
| committer | Atneya Nair <atneya@google.com> | Wed Nov 06 11:40:53 2024 -0800 |
| tree | 0964574fe7ff6b51431cf5fdb1d42d5b1bc39f10 | |
| parent | b0c550dcb2433e2f26fe8f250b299623bf1c894f [diff] |
java FlagImpl: Clear context without instrumentat The original change Idecda9c357f6a92b9b4a63b2ec9b0c04ff441a6d logically conflicted with I4f1872b5d6da5167c69cd236925fee4d622c7487 Add the same logic to else side of the allow_instrumentation block. Test: atest aconfig.test.java Bug: 375288788 Change-Id: I3d19f8ad23a07889a69925118a221d147d13a7b1
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.