commit | fa07bff60e0ab60d3cb987f025ec5805314197b4 | [log] [tgz] |
---|---|---|
author | Alexander Mishkovets <amishkovets@google.com> | Mon Nov 02 13:56:18 2020 +0100 |
committer | Alexander Mishkovets <amishkovets@google.com> | Tue Nov 17 19:36:05 2020 +0000 |
tree | 479261e6dc4535412ce9d2059713d4e926736ce9 | |
parent | 4ce377034863c03c5f80972e8a72f8c166ba14d9 [diff] |
DO NOT MERGE Fix the order of loading OEM properties Move the OEM property imports so that they take higher precedence over product and can still be overridden by factory properties. Bug: 171304788 Test: manual Merged-In: I31f0a582a5c1c55a42fb213c8269b7829aa27b52 Change-Id: I6e17440714e3e5b3a94ec6e1d2f166080513e1a0
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.