commit | 5a6bc22b52077ed2bee8a386f02c552f673c749b | [log] [tgz] |
---|---|---|
author | Alexander Mishkovets <amishkovets@google.com> | Wed Nov 11 15:25:37 2020 +0100 |
committer | Alexander Mishkovets <amishkovets@google.com> | Thu Nov 12 13:13:15 2020 +0000 |
tree | 9edc95cb9f7231945194fc52ed2c6152afc2504d | |
parent | 6f83343e7eae8fd826770009cabe1827754152f7 [diff] |
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 Change-Id: I0c0be446d5e9af77acfcdeb5145b5776c8d5820f
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.