Suggest using add_soong_config_ macros instead of direct variable assignments

Bug: 190051051
Test: treehugger
Change-Id: Ib77d8af8f926412f6337173927cee6bb1deda2bb
This commit is contained in:
Sasha Smundak 2021-08-24 14:05:19 -07:00
parent 7c16dabfa5
commit 18fd099982
2 changed files with 8 additions and 18 deletions

View file

@ -451,15 +451,10 @@ used. To specify that no properties should be amended for `soc_b`, you can set
The values of the variables can be set from a product's `BoardConfig.mk` file:
```
SOONG_CONFIG_NAMESPACES += acme
SOONG_CONFIG_acme += \
board \
feature \
width \
SOONG_CONFIG_acme_board := soc_a
SOONG_CONFIG_acme_feature := true
SOONG_CONFIG_acme_width := 200
$(call add_soong_config_namespace, acme)
$(call add_soong_config_var_value, acme, board, soc_a)
$(call add_soong_config_var_value, acme, feature, true)
$(call add_soong_config_var_value, acme, width, 200)
```
The `acme_cc_defaults` module type can be used anywhere after the definition in

View file

@ -122,15 +122,10 @@ type soongConfigModuleTypeImportProperties struct {
// }
//
// If an acme BoardConfig.mk file contained:
//
// SOONG_CONFIG_NAMESPACES += acme
// SOONG_CONFIG_acme += \
// board \
// feature \
//
// SOONG_CONFIG_acme_board := soc_a
// SOONG_CONFIG_acme_feature := true
// SOONG_CONFIG_acme_width := 200
// $(call add_sonng_config_namespace, acme)
// $(call add_soong_config_var_value, acme, board, soc_a)
// $(call add_soong_config_var_value, acme, feature, true)
// $(call add_soong_config_var_value, acme, width, 200)
//
// Then libacme_foo would build with cflags "-DGENERIC -DSOC_A -DFEATURE -DWIDTH=200".
//