commit | 42ab8287546bc07217039643e4e277f1242c17a5 | [log] [tgz] |
---|---|---|
author | Kelvin Zhang <zhangkelvin@google.com> | Thu Feb 17 13:07:55 2022 -0800 |
committer | Kelvin Zhang <zhangkelvin@google.com> | Thu Feb 17 13:07:55 2022 -0800 |
tree | ae73df97d1efab17ec0bd206d75fd54161ce9898 | |
parent | 21118bba679d702278caba35260361a508930942 [diff] |
Emit warning when build.prop import can't be resolved Some mountpoints are only available at device runtime, so ignore import failures in release tools. Bug: 214322896 Test: th Change-Id: I1e8c4fb08c6b825fa19c0f0e019dfaf2b03f2927
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.