commit | 8c3ae62e12aed79d352f16a650fdc9dd57e67a01 | [log] [tgz] |
---|---|---|
author | markchien <markchien@google.com> | Wed Nov 20 19:46:00 2019 +0800 |
committer | markchien <markchien@google.com> | Wed Dec 18 20:49:46 2019 +0800 |
tree | 14d0aa16165baf0858e983cae287a10017860795 | |
parent | ba8208cf62f8e266ab69a9d5903261494f60f610 [diff] |
[Tether16] Build Tethering package Create com.android.tethering apex to pack Tethering.apk and framework-tethering.jar together. For go devices, tethering would run in system server process by InProcessTethering.apk Bug: 144320246 Test: -build, boot Change-Id: Id2d68117e99173682908168e99ee28670bd71871
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.