On Thu, Dec 8, 2011 at 7:44 PM, Joerg Wunsch <[email protected]> wrote: > As Xiaofan Chen wrote: > >> With libusb-compat, you do not need to change any codes. It is >> a wrapper for libusb-0.1 API, on top of libusb-1.0. > > That's been my understanding, too. > > But what do we have to do for this? The configure script only tries > to test-compile a small code snippet that includes "usb.h", creates a > reference to usb_get_string_simple(), and then tries to compile and > link this against -lusb. It doesn't care whether this usb.h and -lusb > come from an original libusb-0.1, or from a wrapper (or from an > OS-supplied API-compatible rewrite, as in FreeBSD). The libusb 1.0 > file and function names have been deliberately chosen to be different, > so there's no confusion. (Besides, avrdude already starts detecting > libusb 1.0, but by now, it's only used for USBasp.)
You do not need to do anything. libusb-compat and libusb-0.1 should usually not be installed at the same time. Initially I thought this may have something to do with libusb-0.1, so I was suggesting people to try out libusb-compat instead if they are using libusb-0.1 under Linux or Mac OS X. -- Xiaofan _______________________________________________ avrdude-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/avrdude-dev
