Re: [Libusb-devel] Can't Send Control Messages to usb devicein Windows

[Jason K. <jas...@gm...>]

I tried doing a reconfigure with enable-debug-log and then I removed toggling debug messages in my program, and debug messages didn't show up at all.  I also get the following warning when I try to complie: 

Warning: resolving _libusb_exit by linking to _libusb_exit@4
Use --enable-stdcall-fixup to disable these warnings
Use --disable-stdcall-fixup to disable these fixups
Warning: resolving _libusb_control_transfer by linking to _libusb_control_transfer@32

Not sure if this is related.

On Apr 21, 2010, at 4:17 PM, Pete Batard wrote:

> On 2010.04.22 00:04, Michael Plante wrote:
>> Are you snipping log messages?  If not, and if you're using the prebuilt
>> binary (this advice may not hold true indefinitely, but it is, afaik, true
>> now), you need to call libusb_set_debug with level 4 to get more messages.
> 
> That's what I was about to suggest, but you need to have generated 
> libusb with --enable-toggable-debug during the configure step.
> 
> This should be the case of the binaries I put only.
> 
> Or if you want to have debug always, you need to use --enable-debug-log
> 
> Alternatively, you could modify the test_hid part of xusb to replace it 
> with your function (with a fixed address), as you would then be able to 
> use 'xusb -i -d 20A0:2'. This would eliminate the remote possibility 
> that some other part of your code is interfering.
> 
> I'll try to do just that on my side, using your code, but I'll have to 
> see if I can get a device that returns data with this call.
> 
> Regards,
> 
> /Pete
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Libusb-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-devel