From: Luca Capello <luca@pca.it>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [btsco] configure/make errors
Date: Wed, 19 Jan 2005 15:18:49 +0100 [thread overview]
Message-ID: <41EE6C49.7090908@pca.it> (raw)
In-Reply-To: <1106136920.8190.96.camel@pegasus>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Marcel,
on 01/19/2005 01:15 PM, Marcel Holtmann wrote:
>> after having solved the automake error, configure gave me another one
<cut>
> And again. The bootstrap thing is for making the developer happy,
> because he must call only one program/script for getting the repository
> ready. It is not for others ;)
I know this, but the problem here is that if someone like me (not a
developer, not really a newbie) wants to try his Bluetake BT420EX with
the bluetooth-alsa project, he should go with the CVS (no other released
versions). And so he has some problem, because there're no info about
the requirements (automake-1.7, the Audio Output libraries and the
Bluetooth libraries, even if the last one was my fault, it's quite
obvious that for a Bluetooth project you need the Bluetooth libraries).
So, IMHO also for developers, at least a 'required packages' section
should be added to the README.
BTW, with my patch there's still one program/script ;-)
> You can also use AM_PATH_BLUEZ. Since bluez-libs-2.13 it is also
> available now, because not all systems use pkg-config.
Ok, I'll add this ASAP, but ATM Debian unstable still has 2.11 and I
should prepare my own Debian bluez-2.13 packages.
Thx, bye,
Gismo / Luca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFB7mxJVAp7Xm10JmkRAoecAJ9i3Uwbz9Cf5OcAIw54Si06BlWGLQCfUNrk
Cswut1XKBFQrwuQ1+04IiHA=
=QquH
-----END PGP SIGNATURE-----
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-01-19 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 21:24 [Bluez-devel] [btsco] configure/make errors Luca Capello
2005-01-19 12:15 ` Marcel Holtmann
2005-01-19 14:18 ` Luca Capello [this message]
2005-01-19 16:21 ` Marcel Holtmann
2005-01-19 19:25 ` 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=41EE6C49.7090908@pca.it \
--to=luca@pca.it \
--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