From: Rogue <roguexz@gmail.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] A few questions about bluetooth-alsa project
Date: Tue, 03 Jul 2007 21:25:02 +0530 [thread overview]
Message-ID: <468A7156.1050708@gmail.com> (raw)
In-Reply-To: <d89ddf300707021858u2e5e8f80k35794595254736f6@mail.gmail.com>
Brad Midgley wrote:
> hey
>
> So first up, I have built sample spec files that generate rpm
> files out
> of sbc and plugz. In case you are interested then I can share them
> with
> you all.
>
>
> sure... I could put them in contrib/
>
Do you want me to send them directly to you?
Secondly, if I build an rpm of plugz, i see that the following files are
being generated:
plugz /etc/dbus-1/system.d/a2dpd.conf
plugz /usr/bin/a2dpd
plugz /usr/bin/a2dpd_ctl
plugz /usr/bin/headsetd
plugz /usr/lib/alsa-lib/libasound_module_ctl_sco.a
plugz /usr/lib/alsa-lib/libasound_module_ctl_sco.la
plugz /usr/lib/alsa-lib/libasound_module_ctl_sco.so
plugz /usr/lib/alsa-lib/libasound_module_ctl_sco.so.0
plugz
/usr/lib/alsa-lib/libasound_module_ctl_sco.so.0.0.0
plugz /usr/lib/alsa-lib/libasound_module_pcm_a2dpd.a
plugz /usr/lib/alsa-lib/libasound_module_pcm_a2dpd.la
plugz /usr/lib/alsa-lib/libasound_module_pcm_a2dpd.so
plugz /usr/lib/alsa-lib/libasound_module_pcm_a2dpd.so.0
plugz
/usr/lib/alsa-lib/libasound_module_pcm_a2dpd.so.0.0.0
plugz /usr/lib/alsa-lib/libasound_module_pcm_sco.a
plugz /usr/lib/alsa-lib/libasound_module_pcm_sco.la
plugz /usr/lib/alsa-lib/libasound_module_pcm_sco.so
plugz /usr/lib/alsa-lib/libasound_module_pcm_sco.so.0
plugz
/usr/lib/alsa-lib/libasound_module_pcm_sco.so.0.0.0
plugz /usr/lib/liba2dpdcommon.a
plugz /usr/lib/liba2dpdcommon.la
plugz /usr/lib/liba2dpdcommon.so
plugz /usr/lib/liba2dpdcommon.so.0
plugz /usr/lib/liba2dpdcommon.so.0.0.0
plugz
/usr/share/dbus-1/services/com.access.a2dpd.service
I see that there are some alsa-lib modules being built. So, do I still
need to specify a custom asoundrc file? Wouldn't the device show up
automatically in the applet's preferences?
I am sorry if these are ignorant questions, but I am trying to learn
what I can about this package. Regarding the work that Marcel is doing
for bluez utils audio service, is there a project / development package
that I can play around with?
thanks,
Rogue
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-07-03 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 20:33 [Bluez-devel] A few questions about bluetooth-alsa project Rogue
2007-07-03 1:58 ` Brad Midgley
2007-07-03 3:31 ` Marcel Holtmann
2007-07-03 15:55 ` Rogue [this message]
2007-07-03 16:40 ` Frederic Dalleau
2007-07-03 16:56 ` Frederic Dalleau
2007-07-11 20:14 ` Rogue
2007-07-03 18:14 ` Brad Midgley
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=468A7156.1050708@gmail.com \
--to=roguexz@gmail.com \
--cc=bluez-devel@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox