| commit | 28ffd7359131132afcee456a71c4a6541306c501 | [log] [tgz] |
|---|---|---|
| author | Yifan Hong <elsk@google.com> | Fri Mar 13 13:11:10 2020 -0700 |
| committer | Yifan Hong <elsk@google.com> | Fri Mar 13 18:32:07 2020 -0700 |
| tree | 2c3b10bc2fd4c838534cc0cb34d68ad70a79874f | |
| parent | 07ea2c03609cfecc99d07afbccb29e8fbbe0c6b6 [diff] |
Proper checks for vendor and ODM SKUs If DEVICE_MANIFEST_FILE / ODM_MANIFEST_FILES is set, also include check for empty vendor / odm SKU, respectively. Then, do cross product of vendor SKUs and ODM skus, and check each possible combination. Test: build with and without vendor skus Test: m check-vintf-all Bug: 148601741 Change-Id: I23cc81998e7afc36c43540bf6d615b4d4b288447
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.