| commit | 69430e65fe5b293415714a4975d60d25963dbfa6 | [log] [tgz] |
|---|---|---|
| author | Yifan Hong <elsk@google.com> | Tue Mar 17 15:18:34 2020 -0700 |
| committer | Yifan Hong <elsk@google.com> | Tue Mar 17 20:27:32 2020 -0700 |
| tree | 423d161d9af535e4d2ad8826ea9927239c0058f1 | |
| parent | 610cbc900ef7822a19e0637bff43c113e00e5ab8 [diff] |
Also check empty SKU if SKUS are not defined In the case when both ODM_MANIFEST_SKUS and ODM_MANIFEST_FILE are both empty, also checks VINTF compatibility for empty SKU case. Same for device manifest. Although right now, DEVICE_MANIFEST_FILE and DEVICE_MANIFEST_SKUS cannot be both empty (because libvintf requires vendor manifest exists barring manifest fragments), let libvintf throws an error for this case. In the build system, simply handle vendor manifest the same way as ODM manifest. Bug: 148601741 Test: manual Change-Id: Ia0655fd4d37f6286b164a3221ec4b2716f29147d
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.