SUSHMITAH / btstack

Automatically exported from code.google.com/p/btstack
0 stars 0 forks source link

Linux build or usage is difficult #172

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
-Werror is specified for builds, but you have #pragma statements everywhere 
that produce a warning, with -Werror makes the build fail.

The vendor/product really needs to be in a config file or as a command line 
option.  There is still a "doesn't work" note in ./configure --help.

And although I have about 6 different kinds of bluetooth dongles, I don't think 
ANY work under your stack under linux.  Do you or anyone know of any chipsets, 
products, or vendor/product IDs that are known to work?  Or is there a way to 
tell?

I could really use this on an embedded ARM board as the standard stack is big, 
but I do need a dongle that works.

Original issue reported on code.google.com by tz2026 on 22 Jun 2011 at 1:20

GoogleCodeExporter commented 8 years ago
hi..

 * #pragma mark:  I've found a way to keep the #pragma mark feature with Xcode without causing harm, see r1228

 * vendor/product would need to be made configurable, once it is working - agreed. We can add command line parameters, BTdaemon already uses getopt

 * the code for HCI USB is an early alpha version and doesn't work, I think. The "doesn't work" in configure.in is correct. For what I know, all USB Bluetooth dongles are equal (aside from some that might need a firmware, those are useless).

Simon tried hard for a while to get USB working and claimed it worked for him. 
I couldn't verify that yet, but commited his changes in r1229. Please try your 
dongles with this and report back. 

Original comment by matthias.ringwald@gmail.com on 23 Jun 2011 at 6:53

GoogleCodeExporter commented 8 years ago
did you try again?

Original comment by matthias.ringwald@gmail.com on 9 Jul 2011 at 10:20