I found some step-by-step instructions on how to call _open and _free_device_list, for instance, that didn't go on to state that I then had to claim an interface before using it. listdevs.c was great for finding the device I needed, but it took a while to figure out that libusb_claim_interface() wasn't needed. Is it not possible to simply have this function accept an int arg?ģ) the documention is copious but I would have benefitted from an overview of USB, such as what 'configurations' and 'endpoints' are.Ĥ) initial projects also seem to go much faster with good hello-world examples. Is there a reason these cannot be defined as having one element?Ģ) since most functions return a return code into an int, it requires a cast to call libusb_strerror() without a warning or error.
This causes compiler warnings as VC++ 2008 doesn't define _STDC_VERSION_. It was easy to download and write working code, thanks!ġ) libusb.h has three structs with arrays with 0 elements. The documentation for libusb-compat says not to install it alongside libusb-0.1, but I'm not sure how to remove libusb-0.1-4. Instead, port your application to use libusb-1.0's asynchronous transfer API, which supports transfer cancellation. With libusb-1.0 or libusb-compat-0.1 backed by libusb-1.0, forcefully killing threads in this way is likely to cause all libusb I/O to halt. I was able to use this to write Visual C++ 2008 code on Windows 7 that talks to a FadeCandy to control my Christmas tree lights. Install Libusb Compat Ubuntu Server - bestgfil.
