From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: loody <miloody@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: some questions about Bluez
Date: Thu, 10 Mar 2011 12:37:54 -0300 [thread overview]
Message-ID: <20110310153754.GA2190@joana> (raw)
In-Reply-To: <AANLkTims_WHKQ4pNPZNgWS390ASeU8Kw1=w4LN2TOsR3@mail.gmail.com>
Hi Loody,
* loody <miloody@gmail.com> [2011-03-10 20:33:49 +0800]:
> hi all:
> I have some questions about bluetooth.
> 1. how many additional libs that I need to successfully compile bluez?
> so far as I know are:
> a. DBUS
> b. GLIB
> c. ALSA
> d. GSTREAMER
> e. USB
> f. SNDFILE
> g.CAPNG
> am I right?
>
> 2. I try to compile Bluez to run on mips platform.
> What I need is a simple tool which can tell me what kind of bluetooth
> device around my usb bluetooth controller.
> it seems I only need to enable USB lib above, right?
>
> 3. from configure, I found we can turn off features by setting
> "--disable-xxxx", so I use below configure command for configuring
> ./configure --prefix=/media/sdb1/bluez-4.89.mips/build
> --host=mipsel-linux-gnu --disable-optimization --disable-fortify
> --disable-pie --disable-network --disable-serial --disable-input
> --disable-audio --disable-service
>
> but it still complain to me that he cannot find alsa header files and libs.
The ./configure line you provided work for me in x86_64. Can you provide the
logs of ./configure && make?
--
Gustavo F. Padovan
http://profusion.mobi
next prev parent reply other threads:[~2011-03-10 15:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 12:33 some questions about Bluez loody
2011-03-10 15:37 ` Gustavo F. Padovan [this message]
2011-03-10 19:01 ` loody
2011-03-10 19:29 ` Gustavo F. Padovan
2011-03-11 1:23 ` loody
2011-03-11 2:38 ` Gustavo F. Padovan
2011-03-11 3:05 ` loody
2011-03-11 5:10 ` Arun K. Singh
2011-03-11 6:25 ` loody
2011-03-11 13:37 ` Anderson Lizardo
2011-03-15 14:27 ` loody
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=20110310153754.GA2190@joana \
--to=padovan@profusion.mobi \
--cc=linux-bluetooth@vger.kernel.org \
--cc=miloody@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