fails to build on iojs 3.2.0 (on Fedora 22) about node-bluetooth-hci-socket HOT 7 CLOSED

@jrobeson looks ok, the optional node-usb dependency is failing, I'll update the read me to mention this.

from node-bluetooth-hci-socket.

@sandeepmistry This is also failing on windows which makes it unusable there as far as I can see. I know this isn't your issue as it's with the underlying node-usb library (from issue node-usb/node-usb#89 and pull request node-usb/node-usb#90) however it's something to note. Also why use raw usb instead of the rfcomm stack? What's missing from that stack?

from node-bluetooth-hci-socket.

@paullryan RFCOMM is not an option for BLE, you need lower level L2CAP or HCI sockets. This module only needs USB access on Windows, on Linux it uses kernel HCI sockets (hence the optional).

If there's a better way to specify a Windows only dependency in the package.json, please let me know.

from node-bluetooth-hci-socket.

@sandeepmistry Thanks for the answer on the needs for windows. I understand the dependency check and that's an acceptable mechanism at this point, I was just pointing out that with node v4.0.0 + it's currently failing on Windows given the nan2 needs for that. Again not your issue (it's a problem in node-usb) but just wanted to make you aware if it comes up again.

from node-bluetooth-hci-socket.

@paullryan thanks for the clarification.

Does it make sense to create another issue to track Node.js 4.0+ not being able to work until node-usb issues are sorted out? Linux and OS X should be fine for 4.0+ as far as I can tell.

from node-bluetooth-hci-socket.

@sandeepmistry probably a good idea, added #7.

And yes you're correct it looks like OS X and Linux are compiling and running fine with NaN2 and Node.js 4.x+

from node-bluetooth-hci-socket.

@paullryan great, thanks for opening #7!

from node-bluetooth-hci-socket.