| commit | 8820eaa5e5db252b1a3211f811fbc0725d926663 | [log] [tgz] |
|---|---|---|
| author | David Anderson <dvander@google.com> | Mon Nov 16 18:31:07 2020 -0800 |
| committer | David Anderson <dvander@google.com> | Wed Nov 18 22:12:34 2020 -0800 |
| tree | cb9b1f5f20cb5d89444373af870db9281ec2717c | |
| parent | a39ec91fbe62d7ba422a917e07f90f5002867118 [diff] |
Move snapuserd into the vendor ramdisk. For devices that are GKI capable, including virtual_ab_ota_compression will now include snapuserd in the vendor ramdisk. For devices that are not GKI-capable (eg do not have vendor_boot), virtual_ab_ota_compression_retrofit.mk must be included in addition to virtual_ab_ota_compression.mk. This structure is to avoid needing a large combination of different Makefiles. Bug: 173463595 Test: manual test Change-Id: Idc740d3523c2d166dd578cee41ea07d7eaf8edfa
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.