commit | b5195ff5fee5500b92ed7a50d6cc1c5ec8c29109 | [log] [tgz] |
---|---|---|
author | Devin Moore <devinmoore@google.com> | Fri Feb 11 18:44:26 2022 +0000 |
committer | Devin Moore <devinmoore@google.com> | Fri Feb 11 18:44:26 2022 +0000 |
tree | 52f94e0a52216e671cf7a0e2b9e74db64ada3028 | |
parent | ea586a8d71d6fbccce1a00e84e38e12f80c34f1a [diff] |
Get build.prop for init_boot.img from the ramdisk props boot.img and init_boot.img get their build properties from the platform ramdisk properties. Test: "m dist" then drop the OTA zip file into android.github.io/analyseOTA to verify init_boot is present. Bug: 211823573 Change-Id: I411e62bf0fc3cb49d4b12dadb52d9820fca041fa
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.