libusb woes on Mac OSX and Windows

News, rumors, and other broad discussion topics.
Post Reply
tcwan
Posts: 186
Joined: 30 Sep 2010, 07:39

libusb woes on Mac OSX and Windows

Post by tcwan »

Hi,

I'm trying to find out if anyone has successfully managed to get nxt-python (which depends on libusb) working on Mac OSX (10.6.6) and Windows (XP SP3) before. If anyone managed to get libusb working with any python package (e.g., nxt-python) for accessing the NXT from either Mac OSX or Windows, I'd like to find out your configuration.

I've tried both platforms, installing the following packages:

On Mac OSX (using MacPorts):
[Config A]
libusb-1.0.8_0, libusb-compat-0.1.3_0
py26-pyusb-0.4.2
nxt-python-2.1.0 (using a local Portfile)

[Config B]
libusb-1.0.8.20101017 (this is tweaked to solve a library symbol problem)
py26-pyusb-devel-1.0.0-a1_0
nxt-python-2.1.0 (using a local Portfile)

With Config A, it does not connect (nxt_test from nxt-python can't find the brick), whereas with Config B, it segfaults.

On Windows XP SP3, the config is:
[Config C]
python-2.6.6
libusb-win32-bin-1.2.2.0
pyusb-1.0.0-a1
nxt-python-2.1.0

With Config C, attempting to call nxt_test will result in an Access Violation.

So currently there is no working setup on Mac OSX or Windows which uses libusb to communicate with the NXT for me.

Feedback appreciated,
T.C.
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest