commit | 8916a2a13c5b2efdff3dff5bdd687f73be5901b7 | [log] [tgz] |
---|---|---|
author | David Anderson <dvander@google.com> | Tue Sep 18 15:46:59 2018 -0700 |
committer | David Anderson <dvander@google.com> | Tue Sep 18 15:53:40 2018 -0700 |
tree | 1fb2b8d19ed12977b37db47dfc06c5ce77fb7b88 | |
parent | 3ea8ca5ac7d11684bf7030d1f1ddab93f59946a9 [diff] |
Don't pass --setup_as_rootfs_from_kernel when using a super partition. When the system partition is a dynamic partition, the device will be using an initial ramdisk and should not have a root device specified on the kernel command-line. Bug: 115939310 Test: device boots when BOARD_SUPER_PARTITION_PARTITION_LIST contains super and AVB is enabled. Change-Id: I5c4b2304bf1ab6a59443c43c354845bf8a3949f0
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.