commit | 7b7af5425966566fab3aebd1e154ef675539d090 | [log] [tgz] |
---|---|---|
author | Remi NGUYEN VAN <reminv@google.com> | Wed Oct 30 15:38:35 2019 +0900 |
committer | Remi NGUYEN VAN <reminv@google.com> | Wed Nov 06 10:27:20 2019 +0000 |
tree | c066e3a929a1d0d76c06836f82a748a134559c6c | |
parent | e8d9df122aa338bbd246d1f1bdfae44f8031dc71 [diff] |
Use NetworkStackNext as preinstalled network stack NetworkStackNext is the build of the network stack targeted at the next API, e.g. system_current and not system_29. While NetworkStack is a mainline module that needs to be built with a stable SDK (system_29), NetworkStackNext is necessary to test functionalities that require the in-development SDK (system_current). Using NetworkStackNext preinstalled on development builds allows for testing the new APIs and functionalities. NetworkStackNext is also configured with a mainline module package name on targets that use mainline modules; but it is not intended to receive mainline updates. Once system_current is finalized (system_30 ?), NetworkStack can start using it, and the system image should switch back to NetworkStack instead of NetworkStackNext. Bug: 139269711 Test: Built, phone boots, WiFi working Change-Id: I885b2c441b99daa3165a4a365738682958478291
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.