| commit | 804ca70cb7a11d603e7d2e1a1baed008ecbc3cd1 | [log] [tgz] |
|---|---|---|
| author | Roshan Pius <rpius@google.com> | Fri Jun 07 07:15:41 2019 -0700 |
| committer | Roshan Pius <rpius@google.com> | Tue Aug 13 09:57:16 2019 -0700 |
| tree | 7a18f7b59c39d53cef18dbceafb1953e0c6670b7 | |
| parent | 0b0627971967eab2ea104fa2fb656c8805afbd9b [diff] |
product: Mainline wifi module Move wifi services into a separate APK. For now, the wifi stack will run inside system_server for all devices. In the future, when the wifi stack becomes a mainline module: For regular devices, the wifi stack will be loaded into the network stack process - WifiStack.apk. For GO (low memory) devices, the wifi stack will be always loaded into system_server - InProcessWifiStack.apk. Bug: 113174748 Change-Id: I1a272cbbb6a5284850177db41ec27a6f6035bb03
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.