commit | 57e8549480d6ea1c823529a42e90ec7c7bb09c5a | [log] [tgz] |
---|---|---|
author | Remi NGUYEN VAN <reminv@google.com> | Fri Jan 07 13:07:49 2022 +0900 |
committer | Remi NGUYEN VAN <reminv@google.com> | Mon Jan 24 18:51:03 2022 +0900 |
tree | b59a4163fb26f67a2cba433cdc74aef723b6fbf0 | |
parent | b5d007b2f86a491da5ce0322523b240823c55ce0 [diff] |
Move nearby apex to tethering Nearby will be merged together with the tethering/connectivity APEX, so that module maintenance efforts can be reduced, and the two codebases can evolve the interfaces that they expose to each other over time. Bug: 189355156 Test: m Change-Id: I51ba3fe8bee34fa226fa5ed31ff9f87ee61fdd63
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.