| commit | 27f5e69636ed96a6d455656976317a368a655499 | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Tue Oct 22 16:30:54 2024 -0700 |
| committer | Cole Faust <colefaust@google.com> | Tue Oct 22 16:30:54 2024 -0700 |
| tree | 1b762d90c15e809649929ea7e613e0c82d695628 | |
| parent | 51bca98727ca51d1b41059bdc510270b29c7d849 [diff] |
Remove dependencies on the 1-variant fallback When adding a dependencies, if the variants don't match, but the dependency only has 1 variant anyways, soong will always use that variant. This makes it hard to add new variants to soong, because the 1-variant fallback stops being used and you start getting missing variant errors. Make changes to bp files such that all dependencies correctly specify the variant to use. Bug: 372091092 Flag: EXEMPT refactor Test: m nothing Change-Id: Ib135116e5c6970f77e34161c23dfa26c567e4d6e
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.