| commit | 9848be3581345ec4e8ca03838cbf0b8af3ed3b0a | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Mon Dec 18 10:34:26 2017 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Thu Dec 21 12:13:13 2017 +0900 |
| tree | d4845ed6bf1d53aff5defc6ce5ec2ac3746d4562 | |
| parent | 7f0e221942a3b79d47273b7ec670add25908f854 [diff] |
TARGET_COPY_OUT_[ODM|OEM] are exported to soong The two make vars are exported to soong as OdmPath and OemPath. Bug: 68187740 Test: out/soong/soong.variables has OdmPath and OemPath each of which points to 'odm' and 'oem'. Change-Id: Ia283e4eb4aacc61b5b3c46e9001ea924566ea898
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.