Re: [Libusb-devel] libusb-1.0 windows backend now in Cygwin packages

[Pete B. <pb...@gm...>]

On 2010.10.03 13:06, chemelli wrote:
> In the code of the app I was trying to compile I had to do a small change:
>
> LIBUSB_API	->	LIBUSB_CALL

Yes, we recently changed the name of that macro. The last cygwin package 
would have used the old one.

> I still get from time to time "libusb_handle_events returned with -1" and
> "usb bulk write failed : ret = -1". So I'm wondering if libusb is considered
> stable under Cygwin or there are some known issues...

The libusb backend is still fairly new, so it is better considered as 
experimental at this stage. Of course, we're trying to iron out any 
potential bug, so if you can tell us more about the conditions under 
which those error appear, that would help. Telling us more about the 
device you are communicating with, your application, and especially 
providing a debug log would be especially useful.

If you used autogen to recompile libusb, debug logging should already be 
enabled, through the --enable-debug-log option, but of course, if your 
application is GUI only, you will have to redirect the console to see 
that debug output.

Or, as Xiaofan pointed out, providing some form of access to either the 
application (provided we can find a USB device that works with it) or 
its source would also help.

Regards,

/Pete