Clean up RELEASE_MOVE_VCN_TO_MAINLINE To move VCN from the platform to Tethering module, the system defined a RELEASE_MOVE_VCN_TO_MAINLINE flag to indicate whether this modularization should be enabled. Specifically, this flag is used in Android.bp files to teach the build system whether to build VCN into the platform or the module. This CL cleans up the RELEASE_MOVE_VCN_TO_MAINLINE flag and all the relevant flag checks in the build files Bug: 374174952 Test: atest FrameworksVcnTests && atest CtsVcnTestCases Flag: EXEMPT FLAG_REMOVAL Change-Id: I543009be2c7c290a21016257b761c9babb6b3605
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.