neard: use WIRELESS_DAEMON
PATCH v2 1/1 neard: use WIRELESS_DAEMON
Honor WIRELESS_DAEMON when wifi is enable for DISTRO_FEATURE.
--- meta/recipes-connectivity/neard/neard_0.19.bb | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
meta/recipes-connectivity/neard/neard_0.19.bb +2 -1
@@ -40,9 +40,10 @@ do_install:append() { RDEPENDS:${PN} = "dbus" # Bluez & Wifi are not mandatory except for handover +WIRELESS_DAEMON ??= "wpa-supplicant" RRECOMMENDS:${PN} = "\ ${@bb.utils.contains('DISTRO_FEATURES', 'bluetooth', 'bluez5', '', d)} \ - ${@bb.utils.contains('DISTRO_FEATURES', 'wifi','wpa-supplicant', '', d)} \ + ${@bb.utils.contains('DISTRO_FEATURES', 'wifi','${WIRELESS_DAEMON}', '', d)} \ " INITSCRIPT_NAME = "neard"
WIRELESS_DAEMON variable is now set separately from three different recipes. Can you make rather make it a PREFERRED_PROVIDER setting?
Alex
Quoted 33 lines · João Henrique Ferreira de Freitas via lists.openembedded.org
Honor
WIRELESS_DAEMONwhen wifi is enable forDISTRO_FEATURE.Signed-off-by João Henrique Ferreira de Freitas <[email protected]>--- meta/recipes-connectivity/neard/neard_0.19.bb | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)meta/recipes-connectivity/neard/neard_0.19.bb +2
-2@@ -40,9 +40,10 @@ do_install:append() { RDEPENDS:${PN} = "dbus" # Bluez & Wifi are not mandatory except for handover +WIRELESS_DAEMON ??= "wpa-supplicant" RRECOMMENDS:${PN} = "\ ${@bb.utils.contains('DISTRO_FEATURES', 'bluetooth', 'bluez5', '', d)} \ - ${@bb.utils.contains('DISTRO_FEATURES', 'wifi','wpa-supplicant', '', d)} \ + ${@bb.utils.contains('DISTRO_FEATURES', 'wifi','${WIRELESS_DAEMON}', '', d)} \ " INITSCRIPT_NAME = "neard" -=-=-=-=-=-=-=-=-=-=-=-Links: You receive all messages sent to this group.
View/Reply Online (#213490): https://lists.openembedded.org/g/openembedded-core/message/213490
Mute This Topic: https://lists.openembedded.org/mt/111838820/1686489
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Quoted 2 lines · Alexander Kanavin via lists.openembedded.org
WIRELESS_DAEMONvariable is now set separately from three different recipes. Can you make rather make it aPREFERRED_PROVIDERsetting?
That is not right since PREFERRED_PROVIDER works on DEPENDS where as this is a runtime dependency.
This is where we end up with the VIRTUAL-RUNTIME_* variables, which are the best way we have of handling this right now despite my dislike of them.
Cheers,
Richard