commit | 2870d1e3c17c82a14954102922b5eb9b0536786a | [log] [tgz] |
---|---|---|
author | Yifan Hong <elsk@google.com> | Thu Dec 19 13:58:00 2019 -0800 |
committer | Yifan Hong <elsk@google.com> | Thu Dec 19 14:00:03 2019 -0800 |
tree | 91c5556e375fcdb5adf7ed8f6844810490ca7615 | |
parent | 4d5458d1f08cd8a8b34c53d462ad0292c97c96aa [diff] |
Add /system/vendor/odm for VINTF search path Compared with board_config.mk and found this one is missing. Also add docs to explain where are these values from. Test: pass Change-Id: Ic22d75a538657bd286edcae6d95f9ee462911975
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.