Use the ?= operator for assignment to avoid downstream assignment errors
Using the = operator makes it so no one else can assign the system property anymore. Other build targets downstream do try to set these properties explicitly to false. Since no one sets the property before, we can use the ?= operator to apply the values, which still allows other makefiles downstream the chance to the change the value. Bug: 274950131 Test: m Change-Id: I113da6efefccef562bb13cb73087e4b5c7eca453
This commit is contained in:
parent
f6df809336
commit
45ff87c8c7
1 changed files with 6 additions and 6 deletions
|
@ -18,12 +18,12 @@
|
||||||
# Bluetooth LE Audio
|
# Bluetooth LE Audio
|
||||||
PRODUCT_PRODUCT_PROPERTIES += \
|
PRODUCT_PRODUCT_PROPERTIES += \
|
||||||
ro.bluetooth.leaudio_switcher.supported=true \
|
ro.bluetooth.leaudio_switcher.supported=true \
|
||||||
bluetooth.profile.bap.unicast.client.enabled=true \
|
bluetooth.profile.bap.unicast.client.enabled?=true \
|
||||||
bluetooth.profile.csip.set_coordinator.enabled=true \
|
bluetooth.profile.csip.set_coordinator.enabled?=true \
|
||||||
bluetooth.profile.hap.client.enabled=true \
|
bluetooth.profile.hap.client.enabled?=true \
|
||||||
bluetooth.profile.mcp.server.enabled=true \
|
bluetooth.profile.mcp.server.enabled?=true \
|
||||||
bluetooth.profile.ccp.server.enabled=true \
|
bluetooth.profile.ccp.server.enabled?=true \
|
||||||
bluetooth.profile.vcp.controller.enabled=true \
|
bluetooth.profile.vcp.controller.enabled?=true \
|
||||||
|
|
||||||
# Bluetooth HAL and Pixel extension
|
# Bluetooth HAL and Pixel extension
|
||||||
DEVICE_MANIFEST_FILE += \
|
DEVICE_MANIFEST_FILE += \
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue