Return-Path: MIME-Version: 1.0 In-Reply-To: References: From: =?UTF-8?Q?Jo=C3=A3o_Paulo_Rechi_Vita?= Date: Sun, 4 Apr 2010 13:14:35 +0000 Message-ID: Subject: Re: Question about BlueZ's configure script To: Daniel Abraham Cc: linux-bluetooth@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: On Sun, Apr 4, 2010 at 10:40, Daniel Abraham wrote: > In BlueZ's README, dev packages for ALSA, Gstreamer (+ plugins base), > and libsnd are not listed as required or even optional. > > However, the configure script does look for them (although it doesn't > fail if they're missing). > > So my question is: why does it look for them? How do they affect BlueZ > compilation/functionality? > Bluetooth audio profiles are implemented in 3 different ways: as an ALSA driver (soon-to-be deprecated), GStreamer elements (SBC decoder, A2DP sink, etc), and PulseAudio modules (recommended). These last ones lives on PulseAudio's tree, the other two live on bluez' tree, so if configure finds it's headers it enables compilation of the respective modules. -- João Paulo Rechi Vita http://jprvita.wordpress.com/