| commit | 3e061bd1c8b2e2d368c7b2d7d6fe9d445b4a004e | [log] [tgz] |
|---|---|---|
| author | Yifan Hong <elsk@google.com> | Fri Apr 02 16:12:05 2021 -0700 |
| committer | Yifan Hong <elsk@google.com> | Fri Apr 02 16:19:01 2021 -0700 |
| tree | f83afd30d65856250c16cf128ee8dfcbcf19a721 | |
| parent | d2170430feed3f047055ac271914b8d2f372bd99 [diff] |
Fix builds with enforce_vintf_kernel + !kernel If a build has PRODUCT_OTA_ENFORCE_VINTF_KERNEL_REQUIREMENTS set (which is set for P+ builds) but no kernel is built, the original code emits a warning, but it won't be able to build target files package because it depends on kernel_configs.txt and kernel_version.txt without any rules. Properly clear BUILT_KERNEL_CONFIGS_FILE and BUILT_KERNEL_VERSION_FILE so that it won't be depended on in this case. Bug: 184128489 Test: TH + forrest Change-Id: I4b8fbd117f114555cf606e3c3b48eb564dbe786b
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.