| commit | 7ed62ac221f4231906829ca287703d6a987c1245 | [log] [tgz] |
|---|---|---|
| author | Yan Yan <evitayan@google.com> | Tue Oct 22 15:39:55 2024 -0700 |
| committer | Yan Yan <evitayan@google.com> | Mon Dec 02 12:35:09 2024 -0800 |
| tree | c86f47a7d7be0ef2552c769c7467532fac68b17f | |
| parent | fafb83af129f5c992754884f25d5e8408385a169 [diff] |
Include VCN in apex based on the build system flag
This patch includes VCN lib to apex jars when the build system flag
RELEASE_MOVE_VCN_TO_MAINLINE is enabled.
This patch also connects the build system flag to the
soong_config_bool_variable "is_vcn_in_mainline". The
"is_vcn_in_mainline" variable will be used in Android.bp files to
conditionally include VCN in either the Tethering module or
the platform.
Bug: 375213246
Test: flag enabled: VCN libs are in the tethering module
flag disabled: VCN libs are in the platform
Flag: RELEASE_MOVE_VCN_TO_MAINLINE
Change-Id: I6240c0222fab042a8cf1794632358bf855903bba
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.