[Bluez-devel] [btsco] configure/make errors

[Bluez-devel] [btsco] configure/make errors

[Luca Capello]

[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello again,

after having solved the automake error, configure gave me another one
and googling solved it [1]. But, again, no dependencies from libao-dev
is present in the README (and, strangely, automake doesn't complain).

This wasn't enough: make gave me other errors, because it could not find
the Bluetooth dev libraries.

Attached a patch against the current CVS:

* bootstrap:
checking for the existence of /usr/share/aclocal/ao.m4 and exiting with
an error if not present (we cannot use the pkg-config because ao.m4 is
used to generate the configure script)

* configure.in:
used pkg-config to check the presence of the Bluetooth dev libraries

* README:
added more info about dependencies (section Build.0)

Thx, bye,
Gismo / Luca

[1] https://www.redhat.com/archives/fedora-list/2004-December/msg03679.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFB7X6NVAp7Xm10JmkRAtPlAJ46nBk7st7KfzBsSc3+W+4tuc2kNwCfSRBM
uNAdtpcWbvjUmLOm83oUT+E=
=wdn3
-----END PGP SIGNATURE-----

[-- Attachment #2: btsco_cvs-20050118-2128_libao-libbluetooth-check.diff --]
[-- Type: text/plain, Size: 1982 bytes --]

diff -Naur btsco_cvs-20050118-2128/bootstrap btsco/bootstrap
--- btsco_cvs-20050118-2128/bootstrap	2005-01-18 18:11:21.000000000 +0100
+++ btsco/bootstrap	2005-01-18 22:04:32.000000000 +0100
@@ -1,10 +1,19 @@
 #! /bin/sh
 
+# Test for the right automake
 if [ ! `which automake-1.7` ]; then
     echo -e "\n*** You need automake-1.7 to compile this software ***\n"
     exit 1
 elif [ ! `automake --version | grep -q 1.7` ]; then
     AUTOMAKE_VERSION="-1.7"
 fi
- 
+
+# Test for the presence of libao-dev (this cannot be done with
+# pkg-config because we need libao-dev for automake)
+if [ ! -s "/usr/share/aclocal/ao.m4" ]; then
+    echo -e "\n*** You need libao-dev to compile this software ***\n"
+    exit 1
+fi
+
+# All we need for the autotools is installed, so go on
 aclocal$AUTOMAKE_VERSION && autoheader && automake$AUTOMAKE_VERSION --add-missing --copy --ignore-deps && autoconf
diff -Naur btsco_cvs-20050118-2128/configure.in btsco/configure.in
--- btsco_cvs-20050118-2128/configure.in	2004-11-28 07:44:49.000000000 +0100
+++ btsco/configure.in	2005-01-18 22:13:23.000000000 +0100
@@ -5,6 +5,8 @@
 AC_PREREQ(2.50)
 AC_INIT()
 
+PKG_CHECK_MODULES(BTSCO, bluez)
+
 AM_INIT_AUTOMAKE(btsco, 0.2)
 AM_CONFIG_HEADER(config.h)
 
diff -Naur btsco_cvs-20050118-2128/README btsco/README
--- btsco_cvs-20050118-2128/README	2005-01-18 18:11:20.000000000 +0100
+++ btsco/README	2005-01-18 22:04:46.000000000 +0100
@@ -31,10 +31,14 @@
 
   Build
 
+    0. In order to build this project, you need:
+        automake-1.7
+        libao-dev
+        libbluetooth-dev
     1. The CVS repository must be checked out:
         cvs -d:pserver:anonymous@cvs.sf.net:/cvsroot/bluetooth-alsa login
         cvs -d:pserver:anonymous@cvs.sf.net:/cvsroot/bluetooth-alsa co btsco
-    2. After that it must be compiled (you need automake 1.7):
+    2. After that it must be compiled:
         ./bootstrap
         ./configure
         make

Re: [Bluez-devel] [btsco] configure/make errors

[Marcel Holtmann]

Hi Luca,

> after having solved the automake error, configure gave me another one
> and googling solved it [1]. But, again, no dependencies from libao-dev
> is present in the README (and, strangely, automake doesn't complain).
> 
> This wasn't enough: make gave me other errors, because it could not find
> the Bluetooth dev libraries.
> 
> Attached a patch against the current CVS:
> 
> * bootstrap:
> checking for the existence of /usr/share/aclocal/ao.m4 and exiting with
> an error if not present (we cannot use the pkg-config because ao.m4 is
> used to generate the configure script)

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 ;)

> * configure.in:
> used pkg-config to check the presence of the Bluetooth dev libraries

You can also use AM_PATH_BLUEZ. Since bluez-libs-2.13 it is also
available now, because not all systems use pkg-config.

Regards

Marcel




-------------------------------------------------------
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

Re: [Bluez-devel] [btsco] configure/make errors

[Luca Capello]

-----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

Re: [Bluez-devel] [btsco] configure/make errors

[Marcel Holtmann]

Hi Luca,

> > 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.

I don't lead this project and so these are only my two cents. Brad is
responsible and it is actually his decision.

Maybe doing a release once in a while is a good idea, but the problem is
the kernel module is not in that shape that I would accept it. However I
like the idea of doing everything in userspace as an ALSA plugin and
that should be the way to go.

> 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.

Yeah, we really need new packages (btw 2.14) for Debian Sid.

Regards

Marcel




-------------------------------------------------------
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

Re: [Bluez-devel] [btsco] configure/make errors

[Brad Midgley]

guys

>>So, IMHO also for developers, at least a 'required packages' section
>>should be added to the README.

yes, that's a no-brainer :) and I added it to the docs

the README is just generated from our main web page 
http://bluetooth-alsa.sf.net

brad


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel