| commit | 66377664336814fa06df8c080b93b8ebdaf74e48 | [log] [tgz] |
|---|---|---|
| author | Mark Chien <markchien@google.com> | Sat Nov 30 04:36:15 2019 -0800 |
| committer | android-build-merger <android-build-merger@google.com> | Sat Nov 30 04:36:15 2019 -0800 |
| tree | 56df282c28e6457ac6d2f0dccfd7b5ab67517836 | |
| parent | 0820c97eecbc8307b5f068e182d5d4b962ee597b [diff] | |
| parent | 2fd7f8e202dd9f79ce850dc54b3cd814a3e3d676 [diff] |
[automerger skipped] Merge "[Tether08] build InProcessTethering package" am: 05c8db112a am: d8c7549b22 am: 2fd7f8e202 -s ours am skip reason: change_id I680273a3ee8fed3af843a829da17ca84b130f475 with SHA1 1542743b88 is in history Change-Id: If278015cdf0d238e88fe7f4c39d8d5a470a08926
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.