From 2db7692a74feb5a38f1d14d23c50d91be68c782c Mon Sep 17 00:00:00 2001 From: Jiyong Park Date: Wed, 8 Nov 2017 16:03:48 +0900 Subject: Add [soc|device|product]_specific Added three properties (soc_specific, device_specific, and product_specific) that shows what a module is specific to. `soc_specific: true` means that the module is specific to an SoC (System-On-a-Chip) and thus need to be installed to vendor partition. This has the same meaning as the old `vendor: true` setting. `device_specific: true` means that the module is specific to the entire hardware configuration of a device includeing the SoC and off-chip peripherals. These modules are installed to odm partition (or /vendor/odm when odm partition does not exist). `product_specific: true` means that the module is specific to the software configuration of a product such as country, network operator, etc. These modules are installed to oem partition (or /system/oem when oem partition does not exist). These modules are assumed to be agnostic to hardware, so this property can't be true when either soc_specific or device_specific is set to true. Bug: 68187740 Test: Build. path_tests amended. Change-Id: I44ff055d87d53b0d2676758c506060de54cbffa0 --- android/variable.go | 2 ++ 1 file changed, 2 insertions(+) (limited to 'android/variable.go') diff --git a/android/variable.go b/android/variable.go index 155eee56c..6962b0fcb 100644 --- a/android/variable.go +++ b/android/variable.go @@ -174,6 +174,8 @@ type productVariables struct { CFIIncludePaths *[]string `json:",omitempty"` VendorPath *string `json:",omitempty"` + OdmPath *string `json:",omitempty"` + OemPath *string `json:",omitempty"` ClangTidy *bool `json:",omitempty"` TidyChecks *string `json:",omitempty"` -- cgit v1.2.3-59-g8ed1b