From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluez-utils-3.11 and configure
Date: Wed, 06 Jun 2007 14:50:53 +0200 [thread overview]
Message-ID: <1181134253.13429.150.camel@violet> (raw)
In-Reply-To: <200706060847.21565.dennisveatch@bellsouth.net>
Hi Dennis,
> Um I might be totally out in left field here but there seems to be some
> deficiencies with the build process in that all the files are not getting
> installed during make install.
>
> I have tried configure with --enable-all and specifying all the configure
> switches individually with the same results. From what I can tell the
> following files do not get installed from the source tree;
>
> audio/asound.conf
> common/libhelper.a
> common/test_textfile
> daemon/auth-agent
> daemon/passkey-agent
> daemon/bluetoothd
> eglib/libeglib
> hcid/libhciserver.a
> hcid/service-did.xml
> hcid/service-ftp.xml
> hcid/service-opp.xml
> hcid/service-spp.xml
> sbc/sbcdec
> sbc/sbcenc
> sbc/sbcinfo
> sbc/libsbc.la
> sdpd/libsdpserver.a
> test/apitest
> test/attest
> test/bdaddr
> test/hsmicro
> test/hsplay
> test/hstest
> test/lmptest
> test/scotest
> test/sdptest
> tools/hcisecfilter
> tools/ppporc
all of these are _NOT_ installed on purpose. As simple as that.
Regards
Marcel
-------------------------------------------------------------------------
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-06-06 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 12:47 [Bluez-devel] bluez-utils-3.11 and configure Dennis Veatch
2007-06-06 12:50 ` Marcel Holtmann [this message]
2007-06-06 14:01 ` Dennis Veatch
2007-06-06 14:46 ` Stefan Seyfried
2007-06-06 14:51 ` Dennis Veatch
2007-06-06 15:44 ` Marcel Holtmann
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=1181134253.13429.150.camel@violet \
--to=marcel@holtmann.org \
--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