| commit | 5057b95572428ee59922431017a37f119c9b006a | [log] [tgz] |
|---|---|---|
| author | Yifan Hong <elsk@google.com> | Thu Jan 07 14:09:57 2021 -0800 |
| committer | Yifan Hong <elsk@google.com> | Thu Jan 07 17:20:22 2021 -0800 |
| tree | ba15fb64aa73fad102908e16096b7e0916268498 | |
| parent | c65a0545dde5b94bf5c622fbc292bcd2e8cb393d [diff] |
Split PARTITIONS_WITH_BUILD_PROP from *_WITH_CARE_MAP Right now they are the same content. In the future, boot will be added to PARTITIONS_WITH_BUILD_PROP, but it is not added to PARTITIONS_WITH_CARE_MAP. Boot partition has a cpio filesystem in the ramdisk, so it contains a build.prop file, but it doesn't make sense to create care map from it. Test: TH Bug: 162623577 Change-Id: I9b5a20fe2d774b52cf7d5eae9deecbc75122a3dd
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.