| commit | 602859b18603fea642cbcd486563f6bfa981eb4d | [log] [tgz] |
|---|---|---|
| author | Kousik Kumar <kousikk@google.com> | Wed Sep 23 08:34:42 2020 +0000 |
| committer | Kousik Kumar <kousikk@google.com> | Wed Sep 23 04:40:24 2020 -0400 |
| tree | dc74149977004d37b1d25835cc380cbd0dc6b18c | |
| parent | 63e1c37e6fb007e5af25f88aee4232735fd15612 [diff] | |
| parent | a7beb10933218c347b67aba9c0a7c2c53d36acf1 [diff] |
resolve merge conflicts of a7beb10933218c347b67aba9c0a7c2c53d36acf1 to rvc-dev Bug: b/167405184 Change-Id: Ib35af2813e7b60932df33f905d8e0398727ee545 Merged-In: I4d06b4fa190d6185b15aa98cb6f1a33f9702981e
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.