| commit | 411fac84d67970b0c06c67c7ab41224166564e3b | [log] [tgz] |
|---|---|---|
| author | Yi-Yo Chiang <yochiang@google.com> | Tue Mar 15 17:40:23 2022 +0800 |
| committer | Yi-Yo Chiang <yochiang@google.com> | Tue Mar 15 18:08:10 2022 +0800 |
| tree | 5326b2af8e2c1ac3da29b8b78b952448f765487b | |
| parent | 5b48aeccb2b409a3a3c746bc3d440d534edf91ba [diff] |
Rename init_boot properties to ro.init_boot.* Right now they're named ro.bootimage.* which is really confusing. Change it so that if generic ramdisk is in boot.img, then name the properties as ro.bootimage.*, otherwise if generic ramdisk is in init_boot.img, then name the prop as ro.init_boot.*. Bug: 211823573 Test: m dist Change-Id: Icff3c7be04b9a3c6490fbf49ba4f05565b029890
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.