| commit | 8bdfe365d6820c670bf8ce229afa48603ca18844 | [log] [tgz] |
|---|---|---|
| author | Yifan Hong <elsk@google.com> | Tue Jan 07 16:35:49 2020 -0800 |
| committer | Yifan Hong <elsk@google.com> | Sat Jan 11 19:06:18 2020 +0000 |
| tree | dfe542eff2ca3ea04c44070c71a2b6840eedef6d | |
| parent | 850f8b5d77d0842979cabc048387128225fc5ab1 [diff] |
Improve BUILT_ASSEMBLED_*_MANIFEST checks They are moved into check-vintf-all, which is more accurate and do not require building full OS images. Also move kernel check code down to check_vintf_compatible. There is no assembled manifest to put kernel configs now, but they are still required for build time OTA VINTF checks. Test: builds Test: change a vintf_fragment file to cause a conflict with main manifest file (add health@2.0 to boot@1.1.xml), and check_vintf_vendor_log fails Change-Id: I9791abc440a40e1537b4387eb67575ff2e22df08
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.