| commit | c0f904e069698c7505674a4f75151380e262cdde | [log] [tgz] |
|---|---|---|
| author | Yifan Hong <elsk@google.com> | Wed Mar 17 11:25:31 2021 -0700 |
| committer | Yifan Hong <elsk@google.com> | Fri Mar 19 12:50:38 2021 -0700 |
| tree | e5bbdf09ca9f3683e21e9603c9d211f9660067a7 | |
| parent | 69973f0aa1516132e659016f7517de9d39aa736c [diff] |
Extracting kernel should not depend on system/vendor build. If system and vendor are built separately, none of the two builds contained kernel information. The process of extracting kernel information shouldn't depend on system and vendor builds, but on the existance of the kernel image. With this change, one of system or vendor build may have INSTALLED_KERNEL_IMAGE defined and the other has PRODUCT_OTA_ENFORCE_VINTF_KERNEL_REQUIREMENTS defined. The one with INSTALLED_KERNEL_IMAGE defined will contain kernel information in target files. After target files are merged, check_target_files_vintf will kick in to do the checks properly. Test: forrest Bug: 180475190 Change-Id: I8d887dd94e1171ab277f02f25534caf098e3faae
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.