| commit | 46a6081c43ca941589793c2f1cc688071aa26f63 | [log] [tgz] |
|---|---|---|
| author | Steven Moreland <smoreland@google.com> | Thu Aug 04 16:35:24 2022 +0000 |
| committer | Steven Moreland <smoreland@google.com> | Thu Aug 04 16:37:57 2022 +0000 |
| tree | 45eed178417fabe9d23fc8f908baf19efe6c2a9e | |
| parent | 5cf821797859eaf29a25ea8e3529426532233110 [diff] |
BOARD_VNDK_VERSION always by default There is a lot of pending cleanup pending on always having the VNDK enabled. For instance, when some devices always build with the core variant, it is impossible to have code excluded from the system variant, since vendor code on non-VNDK devices wouldn't be able to build. This CL merely disables the flag. When it lands, there is a lot of cleanup that would follow. Bug: 122954981 Test: ¯\_(ツ)_/¯ removing untested paths Change-Id: Ia9380fe54729ce1ab37cf0f5e8512be45cd550c7
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.