Hi,
I want to build yocto dizzy release with Bluez5.
I added the following lines in conf/local.conf :
DISTRO_FEATURES_append = "bluez5"
PREFERRED_PROVIDER_bluez-hcidump = "bluez5"
PNBLACKLIST[bluez-hcidump] = "superseded by bluez5"
PNBLACKLIST[gst-plugin-bluetooth] = "dropped from bluez5"
PNBLACKLIST[bluez4] = "superseded by bluez5"
When I try to build this with bitbake command: bitbake core-image-sato
I am getting the following error:
ERROR: Please ensure that your setting of VIRTUAL-RUNTIME_init_manager (sysvinit) matches the entries enabled in DISTRO_FEATURES
ERROR: Failed to parse recipe: /fsl-community-bsp/sources/poky/meta/recipes-extended/packagegroups/packagegroup-core-full-cmdline.bb
I am not sure what I am doing wrong. Please advice.
Regards,
Ashwin
Hello Ashwin,
I’m not familiar with this error but is “bluetooth” part of the DISTRO_FEATURES. I think you need to add “bluetooth” besides “bluez5”. Have you tried this? The rest of the commands look okay. I’ll try to reproduce.
Regards,
Gus
Hi Gus,
It builds Bluez4, so I guess bluetooth” is a part of the DISTRO_FEATURES.
I want to build it with Bluez5.
Instead of DISTRO_FEATURES_append = "bluez5", if I use DISTRO_FEATURES_append += "bluez5", I did not get the above mentioned error.
But, still build fails because of pulse audio and other components. They have dependency on bluez4.
Any Idea how to build Bluez5 instead of bluez4 ?
Regards,
Ashwin
Hello Ashwin,
It may help to have PREFERRED_PROVIDER_bluez4 ?= "bluez5" and of course 'bluetooth' in DISTRO_FEATURES as you mentioned. I haven't tried this fix tough. Please let us know if this helps.
Regards,
Gustavo
Hi Gustavo,
I tried your solution today. The build was with some warnings.
However, when Bluez5 is built, bluetoothd daemon is not created.
Any idea why it was not created?
Regards,
Ashwin
Hello,
I have also tried to build the YOCTO with bluez5 support. I know that default supported version for the bluez is bluez4 but I want support for bluez5. I did following changes in locat.conf file to install the bluez in image.
PREFERRED_PROVIDER_virtual/mesa = ""
DISTRO_FEATURES_append += "bluez5"
PREFERRED_PROVIDER_bluez-hcidump = "bluez5"
PNBLACKLIST[bluez-hcidump] = "superseded by bluez5"
PNBLACKLIST[gst-plugin-bluetooth] = "dropped from bluez5"
PNBLACKLIST[bluez4] = "superseded by bluez5"
PREFERRED_PROVIDER_bluez4 = "bluez5"
DISTRO_FEATURES_remove = "x11 wayland directfb bluez4"
CORE_IMAGE_EXTRA_INSTALL += "libedit bluez5"
When I built the image I found that bluez4 and bluez5 both are installed and I got the conflicting errors for both these and not able to complete the build. Can you help me on this?
Thanks,
Ajay
Hi Ajay,
did you solve your problem?
I had same issue.
The problem is that in your sysroot you already had bluez4 solution installed.
Solution is to comment in local.conf the line you have added and claim
bitbake -c cleansstate bluez4
bitbake -c cleansstate bluez-hcidump
Than add in local.conf
DISTRO_FEATURES_append += "bluez5"
And bitbake your image.
Regards,
Riccardo