commit | 04714da51cb0dcc81dd447e3b36fbb04dbf01b39 | [log] [tgz] |
---|---|---|
author | Garfield Tan <xutan@google.com> | Thu Aug 13 15:21:32 2020 -0700 |
committer | Garfield Tan <xutan@google.com> | Thu Aug 13 18:42:43 2020 -0700 |
tree | 90a515a4517cc0a215be87c9df37a5789f60907d | |
parent | 9c81a78e972d2d99d8524a24cccf31e0808710d7 [diff] |
Include vendor overrides in system prop if not split Bug: 163854285 Test: m on crosshatch. Vendor overrides are included in system/build.prop on legacy devices. Change-Id: Ib134f934de8546af3dff27312f6877eafe5ed22c
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.