| commit | 8086a123c38c7dd2fc80e0484121614674a0bd34 | [log] [tgz] |
|---|---|---|
| author | Roshan Pius <rpius@google.com> | Fri Nov 22 17:11:36 2019 -0800 |
| committer | Roshan Pius <rpius@google.com> | Tue Nov 26 07:13:36 2019 -0800 |
| tree | bd6922c0a81e7651e521ef9d4edd93f8b012298e | |
| parent | 2cea7f94172102e9e3a374cc64a2149ac329fed5 [diff] |
base_system.mk: Switch to wifi mainline apex Also, explicitly include the cacerts_wfa in builds. This used to be included via the "required" tag in wifi-service build rule. We probably don't want to deliver CA certificates to OEM devices via mainline updates. So, leaving it out of the wifi mainline module & explicitly including it in the base makefile. Bug: 144722612 Test: Device boots up & connects to wifi networks. Change-Id: I3e4487f9fad765e442bf8335ec1f21de3a47674d
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.