| commit | 68ab626aacb1fad3a6d6bcac0d2e6edd6f5617a1 | [log] [tgz] |
|---|---|---|
| author | Yo Chiang <yochiang@google.com> | Tue Jan 19 18:14:59 2021 +0800 |
| committer | Yo Chiang <yochiang@google.com> | Tue Jan 19 18:58:43 2021 +0800 |
| tree | 657b67e3d1cbc3821fa6f5a55b797273f878b362 | |
| parent | fc596c996f35e123a0c2430894500aae97b5fde7 [diff] |
Specify --ramdisk_name for vendor ramdisks for vendor_boot v4 When building vendor_boot v4 with multiple vendor ramdisks, pass the name of each ramdisk to mkbootimg. Bug: 177882072 Test: Modify a device BoardConfig and verify the built vendor_boot.img with unpack_bootimg Change-Id: I679d277aa88f1e10678d2f74b579e4140536e267
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.