All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Pulseaudio does not detect ofono and bluez5
Date: Sun, 8 May 2016 18:09:40 +0200	[thread overview]
Message-ID: <572F64C4.2000605@gmail.com> (raw)
In-Reply-To: <572F38E0.3040004@gmail.com>


Found. libsbc was missing.
I guess should automatically selected when pulseaudio is enabled.

Marco

--

Il 08/05/2016 15:02, Marco Trapanese ha scritto:
>
> Compiling pulseaudio with bluez5 and ofono should lead to their support.
> Instead the configure process doesn't detect them as you can see in 
> the Makefile:
>
>> HAVE_ALSA = 1
>> HAVE_AVAHI = 0
>> HAVE_BLUEZ = 0
>> HAVE_BLUEZ_4 = 0
>> HAVE_BLUEZ_5 = 0
>> HAVE_BLUEZ_5_NATIVE_HEADSET = 0
>> HAVE_BLUEZ_5_OFONO_HEADSET = 0
>
> I tried to rebuild pulseaudio after the whole image is generated (i.e. 
> if it was compiled before ofono and bluez5) but with no chance.
>
> Then, I save the output of the rebuilding (attached to this email):
>
>> Enable D-Bus:                  yes
>>       Enable BlueZ 4:              no
>>       Enable BlueZ 5:              no
>>         Enable ofono headsets:     no
>>         Enable native headsets:    no
>
>
> I also see this warning:
>
>> configure: WARNING: unrecognized options: --disable-gtk-doc, 
>> --disable-gtk-doc-html, --disable-doc, --disable-docs, 
>> --disable-documentation, --with-xmlto, --with-fop, --enable-libudev
>
> I also attach the .config file. Please be aware about the changes I 
> made to compile bluez5. Version: Buildroot 
> 2016.05-git-01212-gabfaf47-dirty.
>
> Marco
>
>

      reply	other threads:[~2016-05-08 16:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-08 13:02 [Buildroot] Pulseaudio does not detect ofono and bluez5 Marco Trapanese
2016-05-08 16:09 ` Marco Trapanese [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=572F64C4.2000605@gmail.com \
    --to=marcotrapanese@gmail.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.