| commit | 6b7cc73ec5477e1c4812c95b3a1ae9bcc4722077 | [log] [tgz] |
|---|---|---|
| author | Yifan Hong <elsk@google.com> | Fri Nov 20 12:15:01 2020 -0800 |
| committer | Yifan Hong <elsk@google.com> | Mon Nov 23 15:17:01 2020 -0800 |
| tree | 153ae3fab41ae417b54d68a6d7725ccdf1e12121 | |
| parent | 942987d116983a5991207e8c55a6ec99af41f763 [diff] |
Add Virtual A/B with vendor ramdisk product. If vendor_ramdisk exists, it is preferred to use launch_with_vendor_ramdisk.mk because it moves e2fsck to vendor_ramdisk, making ramdisk smaller. Devices that uses VABC is assumed to have a vendor ramdisk, so inherit from this new makefile. Test: pass Change-Id: If6adad9985ca4750225fd4263edb42de1ddaf486
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.