| commit | bb26c6f2bfde3eb97589e3f27eb848c778ef9b29 | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Tue May 26 03:18:36 2020 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Mon Jun 08 10:09:12 2020 +0900 |
| tree | b007f060c8b8815444710ef91dd7fbe9eb94ed76 | |
| parent | c844de42410f6263525639af1ba390fa187250bb [diff] |
Rule for system/build.prop is also from macro Like other <partition>/build.prop files, the build rule for system/build.prop is also created using the build-properties macro. system/build.prop has a few number of auto-generate properties that the macro doesn't create. Those properties are emitted to intermediate files using manually crafted rules, the paths to the files are fed to the macro, where their contents are copied to system/build.prop. This change also refactors the code fragment that defines BUILD_* variables that identifes the given build. Bug: 117892318 Test: m Change-Id: Ic218283b40fedeaddacb3fda93167edbec86094c
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.