| commit | ef83b80ec3971c70524d0be98dbb2b201ef546e1 | [log] [tgz] |
|---|---|---|
| author | markchien <markchien@google.com> | Thu Oct 17 11:34:48 2019 +0800 |
| committer | Mark Chien <markchien@google.com> | Fri Nov 29 13:50:54 2019 +0000 |
| tree | 387ed14398c3e6e386909f1f68cdb4cbefebd4be | |
| parent | 1567472ff9001d0cbe8a213e78fa3000306ec121 [diff] |
[Tether08] build InProcessTethering package Build tethering package which is running the same process as system server. Since tethering still have some dependency with system server which need to run in system server process(e.g. use LocalService), we need to use InProcessTethering for all first. After cutting off the dependency, Go devices would keep use "InProcessTethering" and other non-Go devices would be switched to use "Tethering" package. Bug: 136040414 Test: -build, flash, boot Change-Id: I680273a3ee8fed3af843a829da17ca84b130f475 Merged-In: I680273a3ee8fed3af843a829da17ca84b130f475
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.