commit | 7dc5117ffd8098374ee528d5a9cd4a8d7906fc95 | [log] [tgz] |
---|---|---|
author | Yifan Hong <elsk@google.com> | Tue Jan 12 11:27:39 2021 -0800 |
committer | Yifan Hong <elsk@google.com> | Tue Jan 12 11:27:55 2021 -0800 |
tree | 718c951bd7419b3cc5ce40b43060f2719f030dcb | |
parent | c275c68dfd9192682a69b8b113ba92823ad0fd11 [diff] |
GetBootImageBuildProp returns None if file does not exist If system/etc/ramdisk/build.prop does not exist in the ramdisk, GetBootImageBuildProp should return None instead of a path to a non-existant file. Test: pass Bug: 177171706 Change-Id: I34e447bc315d203e136e8c0d59d00961f81301e3
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.