mcuee

Ref: the use of variadic poses some challenges for Python bindings. https://github.com/pyusb/pyusb/issues/200 https://github.com/vpelletier/python-libusb1/issues/75#issuecomment-909733308

@pbatard I think that is the best guess for now. The export from VS2019 seems to be easy to understand in most case, at a quick glance, I only see...

So in this case, the merged https://github.com/libusb/libusb/pull/964 may not be totally correct but it probably may not do harm as well. Let's see if people are encountering the issue or...

With libusb-1.0.24 release, there is a reported issue. https://github.com/EttusResearch/uhd/issues/453

@pbatard If your guess is correct, how shall we fix the libusb-1.0.def? Is the following correct? ``` diff --git a/libusb/libusb-1.0.def b/libusb/libusb-1.0.def index e357ef5..648ae6a 100644 --- a/libusb/libusb-1.0.def +++ b/libusb/libusb-1.0.def @@ -155,7...

@pbatard You are being very helpful already. Thanks. Now the question is how to test. This issue report comes from https://github.com/EttusResearch/uhd/issues/453 and based on the testing it is a false...

From libusb-devel mailing list. On Thu, Sep 9, 2021 at 9:53 PM Jef Driesen wrote: > > On 5/09/2021 04:25, Xiaofan Chen wrote: > > https://github.com/libusb/libusb/issues/944 > > Just wondering...

> I'll note that this is a compile time error on clang with MSYS2. Fixed with: > > ``` > --- a/libusb/core.c > +++ b/libusb/core.c > @@ -2181,7 +2181,7 @@...

> @mcuee 32-bit. That strings output was with a 32-bit library. > > MSYS2 GCC behaves the same. The only difference is that it's a silent failure with GCC and...

List: libusb-devel Subject: Re: [Libusb-devel] usb_interrupt_read error when launching From: Alan Stern Date: 2010-08-18 14:16:00 Message-ID: Pine.LNX.4.44L0.1008181006450.1671-100000 () iolanthe ! rowland ! org [Download RAW message or body] On Wed,...