commit | 29445bd9352db633f218e72dd87b7030cd8c1dea | [log] [tgz] |
---|---|---|
author | Kiyoung Kim <kiyoungkim@google.com> | Mon Sep 25 16:25:20 2023 +0900 |
committer | Kiyoung Kim <kiyoungkim@google.com> | Mon Sep 25 16:25:20 2023 +0900 |
tree | 50d9e5b3f744056be9d4ed857f55e2cdfd822b27 | |
parent | 50b8e4fb0d1a0ca1316e56d4a224194f22ec5ce6 [diff] |
Do not compare KEEP_VNDK with false Overall android build system assumes empty value as false, so comparing KEEP_VNDK value with false can cause unexpected problem in the future. It should be changed to compare with true in opposite way. Bug: 299197187 Test: aosp_cf build succeeded with KEEP_VNDK=false Change-Id: I5db685c2735309a14ea6bdb8b8928b2aa987929f
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.