| commit | 357d069f7f7cb9253d5cb1a211df43eabdfb7df9 | [log] [tgz] |
|---|---|---|
| author | Steven Moreland <smoreland@google.com> | Fri Aug 30 23:28:23 2024 +0000 |
| committer | Steven Moreland <smoreland@google.com> | Fri Aug 30 23:28:23 2024 +0000 |
| tree | ab8052e29e3e44c20c9cc798ac8a42f76f5f2e61 | |
| parent | 1dbf5fb0454616d05c2aec48f9aff8fa51eac4a4 [diff] |
Monotonicity for NEED_AIDL_NDK_PLATFORM_BACKEND. Hint to partners this will go away. We have limited testing of this option, and we shouldn't maintain two ways of handling NDK AIDL variants. So, this way we can remove it in the future. :D Bug: 161456198 Test: build Change-Id: I5ae43b4f1b6c0d7253e82caeb338b69b7e00fdb6
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.