commit | 78860164d08cdc7b938bde0496a5a53122c6373e | [log] [tgz] |
---|---|---|
author | Yifan Hong <elsk@google.com> | Wed Oct 28 14:15:21 2020 -0700 |
committer | Yifan Hong <elsk@google.com> | Wed Oct 28 17:05:18 2020 -0700 |
tree | 8225210bbead844fcd41c97fa2fee06457be8804 | |
parent | c56931c1739ef0cbc75fd41e3da9699e5509e1e6 [diff] |
Do not put GENERIC_KERNEL_CMDLINE in recovery image. The GENERIC_KERNEL_CMDLINE should only be in the generic boot image. If device uses recovery-as-boot, it never uses generic boot image because on devices with generic boot image, recovery resources are moved to vendor_boot instead. Bug: 171512004 Test: builds Change-Id: Ia84e604a8ded28af39c7f1861ff5d3b3af55849f
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.