From: "Pali Rohár" <pali.rohar@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: bluez: install a2dp-codecs.h file
Date: Wed, 3 Jul 2019 14:59:04 +0200 [thread overview]
Message-ID: <20190703125904.4fywymmawb52bxb7@pali> (raw)
In-Reply-To: <CABBYNZJvs8SEGVcQPO7ZdkLoKAkWJmjton3wZqOn++u=J6m5=A@mail.gmail.com>
On Monday 15 April 2019 10:58:53 Luiz Augusto von Dentz wrote:
> Hi Pali,
>
> On Sat, Apr 6, 2019 at 5:54 PM Pali Rohár <pali.rohar@gmail.com> wrote:
> >
> > On Sunday 24 March 2019 15:20:58 Pali Rohár wrote:
> > > Hello, some projects like pulseaudio is re-using a2dp-codecs.h file. It
> > > has own private copy of it. To simplify sharing this file between
> > > projects, what do you think about exposing this file as part of bluez
> > > API? That make install would install this file into system and other
> > > projects like pulseaudio could depends on it.
> >
> > Hello, any idea about exporting this a2dp-codecs.h file?
>
> We don't actually need it in BlueZ, well except for BlueZ for Android
> which apparently has no users. But we could have a way to fetch it in
> PulseAudio, afaik that was something similar going on some year back.
BlueZ itself needs it for avinfo tool (tools/avinfo.c). And also it is
used in profiles/audio/a2dp.c file.
--
Pali Rohár
pali.rohar@gmail.com
prev parent reply other threads:[~2019-07-03 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 14:20 bluez: install a2dp-codecs.h file Pali Rohár
2019-04-06 14:52 ` Pali Rohár
2019-04-15 7:58 ` Luiz Augusto von Dentz
2019-07-03 12:59 ` Pali Rohár [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=20190703125904.4fywymmawb52bxb7@pali \
--to=pali.rohar@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox