On Sat, Jun 16, 2012 at 5:28 PM, Xiaofan Chen wrote:
> On Sat, Jun 16, 2012 at 3:22 AM, Pete Batard wrote:
>> I don't think I recompiled at level 4 since last time we tried it in
>> libusb-devel, which was probably more than a year ago.
>> I have now added this item as another task for for the 1.
, do you mean
>> libusbx-1.0.12?
Woops; yes, it's 1.0.12.
>> You can produce detailed debug log if you set the environmental
>> variable LIBUSB_DEBUG to 4. That debug log may help to identify
>> the potential problem.
Ok, I've uploaded it here:
http://gcead
On Sat, Jun 16, 2012 at 11:49 AM, Xiaofan Chen wrote:
> On Sat, Jun 16, 2012 at 2:08 AM, Pete Batard wrote:
>> It is my pleasure to announce the release of libusbx v1.0.12.
>
> Great.
>
> Since you mentioned clang quite a bit, so I tried to build
> this one under Mac OS X with Apple's clang compi
To Ellis: please subscribe to the mailing list. Thanks.
On Sun, Jun 17, 2012 at 9:08 PM, Xiaofan Chen wrote:
> On Sun, Jun 17, 2012 at 7:08 PM, Ellis Whitehead
> wrote:
>> I have a project http://gcead.sourceforge.net/ that records data from
>> an isochronous acquisition device. The USB communi
On Sun, Jun 17, 2012 at 7:08 PM, Ellis Whitehead
wrote:
> I have a project http://gcead.sourceforge.net/ that records data from
> an isochronous acquisition device. The USB communication utilizes
> libusbx on linux and libusb-win32 on windows, and both work fine
> (thanks!).
Great. Thanks for th
On Sun, Jun 17, 2012 at 8:00 PM, Peter Stuge wrote:
> Xiaofan Chen wrote:
>> > Bug report to dlltool (actually invalid as pointed by Kai).
>> > http://sourceware.org/bugzilla/show_bug.cgi?id=14258
>>
>> On the other hand, Ruben disagreed with Kai and he
>> thinks that the library name is optional.
Xiaofan Chen wrote:
> > Bug report to dlltool (actually invalid as pointed by Kai).
> > http://sourceware.org/bugzilla/show_bug.cgi?id=14258
>
> On the other hand, Ruben disagreed with Kai and he
> thinks that the library name is optional.
This is not a subjective matter. MS is the authoritative
On Sun, Jun 17, 2012 at 7:21 PM, Xiaofan Chen wrote:
> I found a strange error when building libusbx with newer version of
> the dlltool. As per this thread, it is the syntax error of libusb-1.0.def
> which caused the problem.
> http://comments.gmane.org/gmane.comp.gnu.mingw.w64.general/5141
>
> I
I have a project http://gcead.sourceforge.net/ that records data from
an isochronous acquisition device. The USB communication utilizes
libusbx on linux and libusb-win32 on windows, and both work fine
(thanks!).
On mac, however, data is frequently dropped, and we see the following
error message r
I found a strange error when building libusbx with newer version of
the dlltool. As per this thread, it is the syntax error of libusb-1.0.def
which caused the problem.
http://comments.gmane.org/gmane.comp.gnu.mingw.w64.general/5141
I tested Kai's modification to add the library name to libusb-1.0.
On Sun, Jun 17, 2012 at 5:03 PM, Jach Fong wrote:
> Hi! Xiaofan,
>
> Thanks for the guidance on choosing the libusb... I think
> I will stick on the -win32 version at this moment, but like to
> experiment with the newer libusbx.
>
> Back to my problem raised in my first mail that a -0x0C
> w
11 matches
Mail list logo
