| commit | 703a048b5c88763017a12d5e8b39af42a4db0a6f | [log] [tgz] |
|---|---|---|
| author | Yan Yan <evitayan@google.com> | Tue Sep 10 20:19:44 2024 +0000 |
| committer | Yan Yan <evitayan@google.com> | Wed Oct 23 20:14:33 2024 +0000 |
| tree | f9adfbef4fe106aec123798d310b9f84c5cba87b | |
| parent | 9aaed5b62696112eb291cde8a421548b6501a249 [diff] |
Add framework-connectivity-b to the boot classpath This is a preparation CL for moving VCN from platform to Tethering module. As the first step, VCN will be built into it's own java_sdk_library on the platform and be loaded into the boot classpath. Followup CLs will move VCN to a mainline module and thus add framework-connectivity-b to PRODUCT_APEX_BOOT_JARS with a flag. This CL also improves the dup check of PRODUCT_APEX_BOOT_JARS and PRODUCT_BOOT_JARS. Previously, it checkes whether the apex jar name is a substring of PRODUCT_BOOT_JARS. It will trigger false alert when there is a "framework-connectivity" in PRODUCT_APEX_BOOT_JARS and a "framework-connectivity-b" in PRODUCT_BOOT_JARS Bug: 369703242 Test: build and boot Flag: EXEMPT create new empty libraries; no functional change Change-Id: I9e5d77c8f5b7b014bde84fd9cc1997852196af37
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.