Without this change, AndroidBoardCommon.mk
is inherited on all devices even if they
are non-QCOM.
This fixes the following errors:
[ 0% 768/138981] Creating /out/jake/target/product/oriole/vendor/bt_firmware
FAILED: /out/jake/target/product/oriole/vendor/bt_firmware
/bin/bash -c "(mkdir -p /out/jake/target/product/oriole/vendor/bt_firmware ) && (ln -sf /vendor/bt_firmware /out/jake/target/product/oriole/root/bt_firmware )"
ln: cannot create symbolic link from '/vendor/bt_firmware' to '/out/jake/target/product/oriole/root/bt_firmware': No such file or directory
[ 0% 769/138981] Creating /out/jake/target/product/oriole/vendor/dsp
FAILED: /out/jake/target/product/oriole/vendor/dsp
/bin/bash -c "(mkdir -p /out/jake/target/product/oriole/vendor/dsp ) && (ln -sf /vendor/dsp /out/jake/target/product/oriole/root/dsp )"
ln: cannot create symbolic link from '/vendor/dsp' to '/out/jake/target/product/oriole/root/dsp': No such file or directory
Change-Id: Id8938d36ae70c5bd3a4462bc875e390e8228cd62
* This allows environments which use this flag for things
like strictly QTI BT to function as expected.
Change-Id: I64321a85d5208bf092a04bf35fea59a43195f8de
- To use this, set TARGET_COMMON_QTI_COMPONENTS := <components>.
e.g. TARGET_COMMON_QTI_COMPONENTS := av bt perf
- Configurations go inside qti-components/<component>/qti-<component>.mk
- Blob list go in qti-components/<component>/proprietary-files.txt
Change-Id: I9868b02da59c69326f3587cf338187753955c1db