Re: [Libusbx-devel] Towards a 1.2.0 release, with hotplug support, and now also BOS / SS EP comp support, please test!

On Thu, May 30, 2013 at 5:12 PM, Hans de Goede wrote: > Not sure if that will cause confusion, the soname and real version not > being related is normal under Linux, if that is different under Windows, > we might consider putting 1.2 in the dll name under Windows. But that is > your call. To be h

Re: [Libusbx-devel] [PATCH] RFC: Add a libusb_strerror() function

On 2013.05.30 16:08, Sean McBride wrote: > Aside: would be nice to add "What is the license?" to the FAQ here: > Done. Regards, /Pete -- Introducing AppDynamics Lite, a fre

Re: [Libusbx-devel] Bulk transfer queueing order problem

On 2013.05.30 14:44, Toby Gray wrote: > The current libusbx windows backend deliberately turns off sending a ZLP > at the end of a transfer: > https://github.com/libusbx/libusbx/blob/master/libusb/os/windows_usb.c#L2651 > It's the disabling of the SHORT_PACKET_TERMINATE: > http://msdn.microsoft.com

Re: [Libusbx-devel] Towards a 1.2.0 release, with hotplug support, and now also BOS / SS EP comp support, please test!

On 2013.05.30 10:12, Hans de Goede wrote: >> Still makes me curious. Do you know of any project where a >> major.nonzero-minor.pc is used? > > ls /usr/lib64/pkgconfig shows 1 on my system: > > lrwxrwxrwx. 1 root root 17 Apr 5 15:48 soundtouch-1.0.pc -> > soundtouch-1.4.pc > -rw-r--r--. 1 root ro

Re: [Libusbx-devel] [PATCH] RFC: Add a libusb_strerror() function

On 2013.05.30 17:24, Orin Eman wrote: > So I'm in the English ASCII only and have done with it camp. Well, I'm firmly in the let's get done with it camp. And like Orin I'm not entirely sure about the whole point of localizing our error strings or just how much usage this localization will actual

Re: [Libusbx-devel] [PATCH] RFC: Add a libusb_strerror() function

The contents of gettext-runtime/COPYING:The gettext-runtime package is partially under the LGPL and partially underthe GPL.The following parts are under the LGPL, see file intl/COPYING.LIB:  - the libintl and libasprintf libraries and their header files,  - the libintl.jar Java library,  - the GNU.

Re: [Libusbx-devel] [PATCH] RFC: Add a libusb_strerror() function

On Thu, May 30, 2013 at 2:30 AM, Hans de Goede wrote: > Hi, > > On 05/30/2013 09:44 AM, Xiaofan Chen wrote: > > On Tue, May 28, 2013 at 6:25 PM, Hans de Goede > wrote: > >> This patch adds the much requested libusb_strerror() function, taking > into > >> account all issues people raised wrt prev

Re: [Libusbx-devel] [PATCH] RFC: Add a libusb_strerror() function

On May 30, 2013, at 10:17 AM, Ludovic Rousseau wrote:2013/5/30 Nathan Hjelm : > > > On May 30, 2013, at 09:08 AM, Sean McBride wrote: > > On Thu, 30 May 2013 09:35:06 +0200, Johannes Stezenbach said: > >>I can't comment on gettext on Windows, only that a qu

Re: [Libusbx-devel] [PATCH] RFC: Add a libusb_strerror() function

2013/5/30 Nathan Hjelm : > > > On May 30, 2013, at 09:08 AM, Sean McBride wrote: > > On Thu, 30 May 2013 09:35:06 +0200, Johannes Stezenbach said: > >>I can't comment on gettext on Windows, only that a quick search >>shows there are several projects using it. Anyway, I trust you >>to do the right

Re: [Libusbx-devel] [PATCH] RFC: Add a libusb_strerror() function

On May 30, 2013, at 09:08 AM, Sean McBride wrote:On Thu, 30 May 2013 09:35:06 +0200, Johannes Stezenbach said: >I can't comment on gettext on Windows, only that a quick search >shows there are several projects using it. Anyway, I trust you >to do the right decision for Windows, but it feels wrong

Re: [Libusbx-devel] [PATCH] RFC: Add a libusb_strerror() function

On Thu, 30 May 2013 09:35:06 +0200, Johannes Stezenbach said: >I can't comment on gettext on Windows, only that a quick search >shows there are several projects using it. Anyway, I trust you >to do the right decision for Windows, but it feels wrong >to not use gettext on Linux and BSD. But you a

Re: [Libusbx-devel] Bulk transfer queueing order problem

On 29/05/13 18:18, qse drf wrote: That's the problem. The supposedly synchronous function calls each return success as I call them in order: OUT 1KB, IN 16B, OUT 1KB, IN 16B But the bus trace shows: OUT 2KB, IN 16B, IN 16B This is the case even if I add a 5 second delay after each call to libus

Re: [Libusbx-devel] [PATCH] RFC: Add a libusb_strerror() function

Hi, On 05/30/2013 09:44 AM, Xiaofan Chen wrote: > On Tue, May 28, 2013 at 6:25 PM, Hans de Goede wrote: >> This patch adds the much requested libusb_strerror() function, taking into >> account all issues people raised wrt previous attempts. >> >> Criteria / Decisions underlying this implementatio

Re: [Libusbx-devel] [PATCH] RFC: Add a libusb_strerror() function

Hi, On 05/30/2013 12:50 AM, Pete Batard wrote: > PS: I also think that if we go for adding a stelocale, it should be > called libusb_setlocale() rather than libusb_set_strerror_locale(). Or > do we plan to have different setlocale for different API calls? Sound reasonable, I will fix this in t

Re: [Libusbx-devel] Towards a 1.2.0 release, with hotplug support, and now also BOS / SS EP comp support, please test!

Hi, On 05/30/2013 12:44 AM, Pete Batard wrote: > On 2013.05.29 12:30, Hans de Goede wrote: >> Hmm, so on posix we only care about the libusb-1.0.pc.in file for the >> files you mention. >> That one definitely needs to stay libusb-1.0.pc.in, since we implement >> an extended >> version of the 1.

Re: [Libusbx-devel] [PATCH] RFC: Add a libusb_strerror() function

On 30/05/2013 10:44, "Xiaofan Chen" wrote: >On Tue, May 28, 2013 at 6:25 PM, Hans de Goede >wrote: >> This patch adds the much requested libusb_strerror() function, taking >>into >> account all issues people raised wrt previous attempts. >> >> Criteria / Decisions underlying this implementation:

Re: [Libusbx-devel] [PATCH] RFC: Add a libusb_strerror() function

On 30/05/2013 10:35, "Johannes Stezenbach" wrote: >How do native Windows programs handle thandle translations? Sorry to jump in, especially as I've not followed the discussion in detail (and the earlier discussion the more or less same discussion on libusb-devel) and not specifically commenting a

Re: [Libusbx-devel] RFC: Add libusb_get_vendor_n_product_string function

On Wed, May 29, 2013 at 8:18 PM, Ludovic Rousseau wrote: > 2013/5/29 Hans de Goede : >> Nope, a libusb_device is just a software struct representing the info >> we could get from the OS about the device without actually opening >> it, or talking to the device. An opened device is represented by >>

Re: [Libusbx-devel] [PATCH] RFC: Add a libusb_strerror() function

On Tue, May 28, 2013 at 6:25 PM, Hans de Goede wrote: > This patch adds the much requested libusb_strerror() function, taking into > account all issues people raised wrt previous attempts. > > Criteria / Decisions underlying this implementation: > -Must support translated messages > -Must not use

Re: [Libusbx-devel] [PATCH] RFC: Add a libusb_strerror() function

On Wed, May 29, 2013 at 11:50:39PM +0100, Pete Batard wrote: > On 2013.05.29 23:25, Hans de Goede wrote: > > Hi, > > > > On 05/30/2013 12:17 AM, Sean McBride wrote: > >> On Thu, 30 May 2013 00:17:11 +0200, Hans de Goede said: > >> > IMHO you should use LC_MESSAGES in the usual way instead > >>