bluez4: use PACKAGECONFIG to control 'pie'
This lets us control whether we build position independent executables. As, as far as I know no distros are adding a 'pie' distro feature, the effect of this commit for most will be to disable pie in bluez4. I think this is best to ensure consistent behavior among the recipes with regard to this. This also sidesteps a build failure I've seen with bluez4 failing due to libudev.a not having been built fPIC. (From OE-Core rev: 06b5d57e89f2dd20fb3f4cb9fd362e2d428f493d) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
e95eff1049
commit
c3bb97b03b
|
@ -10,8 +10,12 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=12f884d2ae1ff87c09e5b7ccc2c4ca7e \
|
||||||
DEPENDS = "udev libusb dbus-glib glib-2.0 libcheck"
|
DEPENDS = "udev libusb dbus-glib glib-2.0 libcheck"
|
||||||
RDEPENDS_${PN}-dev = "bluez-hcidump"
|
RDEPENDS_${PN}-dev = "bluez-hcidump"
|
||||||
|
|
||||||
PACKAGECONFIG ??= "${@base_contains('DISTRO_FEATURES', 'alsa', 'alsa', '', d)}"
|
PACKAGECONFIG ??= "\
|
||||||
|
${@base_contains('DISTRO_FEATURES', 'alsa', 'alsa', '', d)}\
|
||||||
|
${@base_contains('DISTRO_FEATURES', 'pie', 'pie', '', d)}\
|
||||||
|
"
|
||||||
PACKAGECONFIG[alsa] = "--enable-alsa,--disable-alsa,alsa-lib"
|
PACKAGECONFIG[alsa] = "--enable-alsa,--disable-alsa,alsa-lib"
|
||||||
|
PACKAGECONFIG[pie] = "--enable-pie,--disable-pie,"
|
||||||
|
|
||||||
ASNEEDED = ""
|
ASNEEDED = ""
|
||||||
|
|
||||||
|
|
|
@ -1,6 +1,6 @@
|
||||||
require bluez4.inc
|
require bluez4.inc
|
||||||
|
|
||||||
PR = "r1"
|
PR = "r2"
|
||||||
|
|
||||||
SRC_URI += "file://bluetooth.conf \
|
SRC_URI += "file://bluetooth.conf \
|
||||||
file://sbc_mmx.patch"
|
file://sbc_mmx.patch"
|
||||||
|
|
Loading…
Reference in New Issue