bluez5.46: remove testing flag
There is not need to specify the testing flag for bluez5 compilation. That flag is new starting at bluez5.44, and in the past it was called experimental. In the past it made sense to pass that flag to compile specific services, but most of them has been migrated to standard features, and experimental has been renamed to testing, but we do not need any of those testing features. Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
This commit is contained in:
parent
df1876d663
commit
262e7a4b07
|
|
@ -22,8 +22,6 @@ SRC_URI_append_ccimx6qpsbc = " ${QCA6564_COMMON_PATCHES}"
|
||||||
|
|
||||||
inherit update-rc.d
|
inherit update-rc.d
|
||||||
|
|
||||||
PACKAGECONFIG_append = " testing"
|
|
||||||
|
|
||||||
do_install_append() {
|
do_install_append() {
|
||||||
install -d ${D}${sysconfdir}/init.d/
|
install -d ${D}${sysconfdir}/init.d/
|
||||||
install -m 0755 ${WORKDIR}/bluetooth-init ${D}${sysconfdir}/init.d/bluetooth-init
|
install -m 0755 ${WORKDIR}/bluetooth-init ${D}${sysconfdir}/init.d/bluetooth-init
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue