| commit | e51c7e8aefc3d0b2ed69254e56ee46e44ba0b7f4 | [log] [tgz] |
|---|---|---|
| author | Yifan Hong <elsk@google.com> | Thu Nov 19 15:55:43 2020 -0800 |
| committer | Anton Hansson <hansson@google.com> | Wed Dec 09 16:31:25 2020 +0000 |
| tree | 2fa5067bb71262a06d9b16a35c232758741004b7 | |
| parent | d1258eb2f83696f68cd0349ec57d4029662aec06 [diff] |
Set allow list for generic ramdisk Devices that uses generic ramdisk must inherit from generic_ramdisk.mk. This makefile ensures that only a set of files can be installed to the ramdisk. Other files must be installed to the vendor-ramdisk. Let aosp_arm64 use this makefile. Fixes: 173742069 Test: manual Change-Id: Ib2a4a208deaf2f4d707bec256207b4b8479a601a (cherry picked from commit bc9608c4c3f3cd0ac3f29863209c80fcfe4e2f7f)
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.