[PATCH 1/4] bluez 5: Build both headset backends, if available

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 4 November 2014 12:14, David Henningsson
<david.henningsson at canonical.com> wrote:
>
>
> On 2014-11-03 12:47, Peter Meerwald wrote:
>>
>>
>>> Enable both ofono and native backends to be built into the same
>>> libbluez5-util. Never build the null backend.
>>
>>
>> can you please add the check whether bluetooth headers (build
>> dependency) are available in this patch series?
>
>
> Interesting. So it looks like the native backend requires libbluetooth-dev,
> but it does not seem to require to call into anything in libbluetooth.so, so
> we do not need to link to it. If it did, the right thing to do would be to
> do a PKG_CHECK_MODULES(bluez), but now I'm not so sure. Also I'm not sure if
> we need any versioned dependency. I'm ccing Arun and Wim for possible input
> on this issue?

Nope, we just need the header to be there for an inlined function. I
think having the pkg-config check is better than the alternatives.

> Anyhow, it seems not directly related to this patch set, the bug was there
> before. Or was there an uncommitted patch already on the mailing list for
> this issue, in that case I must have missed it?

Yes, the bug was there before, and Peter submitted a patch a few days back.

Cheers,
Arun


[Index of Archives]     [Linux Audio Users]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux