cronet: introduce constant for apex_defaults
Merging them as enabled, so they can be disabled on tm-mainline-prod. Test: TH Change-Id: I5a15acfed68f47b4d59fa72da3dbbce2fd00ae63
This commit is contained in:
@@ -50,6 +50,15 @@ enable_tethering_next_apex = true
|
|||||||
// as the above target may have different "enabled" values
|
// as the above target may have different "enabled" values
|
||||||
// depending on the branch
|
// depending on the branch
|
||||||
|
|
||||||
|
// cronet_in_tethering_apex_defaults can be used to specify an apex_defaults target that either
|
||||||
|
// enables or disables inclusion of Cronet in the Tethering apex. This is used to disable Cronet
|
||||||
|
// on tm-mainline-prod. Note: in order for Cronet APIs to work Cronet must also be enabled
|
||||||
|
// by the cronet_java_*_defaults in common/TetheringLib/Android.bp.
|
||||||
|
cronet_in_tethering_apex_defaults = "CronetInTetheringApexDefaultsEnabled"
|
||||||
|
// This is a placeholder comment to avoid merge conflicts
|
||||||
|
// as cronet_apex_defaults may have different values
|
||||||
|
// depending on the branch
|
||||||
|
|
||||||
apex {
|
apex {
|
||||||
name: "com.android.tethering",
|
name: "com.android.tethering",
|
||||||
defaults: [
|
defaults: [
|
||||||
|
|||||||
Reference in New Issue
Block a user