| commit | b1627779fbaa168fe9a62e759be29dd88cf61771 | [log] [tgz] |
|---|---|---|
| author | Yifan Hong <elsk@google.com> | Wed Jul 14 15:01:50 2021 -0700 |
| committer | Yifan Hong <elsk@google.com> | Thu Jul 15 12:57:47 2021 -0700 |
| tree | f93864085d27936f0655e76216b784b98095d3cd | |
| parent | ff2e24d6f96160730c9a2d4e92a486d96b8788cb [diff] |
Also extract kernel configs from boot image. On devices with prebuilt generic boot image: TARGET_NO_KERNEL := true BOARD_PREBUILT_BOOTIMAGE is set In this case, the process for extracting the kernel config and version must also try extracting from the prebuilt boot image. Test: build on device with prebuilt boot image Fixes: 193588301 Change-Id: I43dd8e206bcd1c9f3f5f51869f126791c50af01a
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.