Sounds good. I'll try to apply this patch for the next release.
/Pete
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/166#issuecomment-30901861--
Rapidly troubleshoot problem
The [Guidelines for Using
SetupAPI](http://msdn.microsoft.com/en-us/library/windows/hardware/ff545011.aspx)
state that if a SetupAPI function fails then the return value of
GetLastError() must be converted to a HRESULT value with the
HRESULT_FROM_SETUPAPI macro before passing it to FormatMessag
I found the root cause of this problem.
I statically linked libusb-1.0 to my main program.
And I also statically linked libusb-1.0 into a DLL library.
In my main program, I opened a device and in the DLL library, I used
libusb_control_transfer to work on the device.
Because of static link, ther
Try adding CFLAGS=-m32-NathanOn Dec 18, 2013, at 07:18 AM, Nothing wrote:./configure --prefix=`pwd`/install --build=i386-linux ac_cv_func_malloc_0_nonnull=yes --disable-udev --with-picI use this comand but the file is still 64bitlibusb-1.0.so.0.1.0: ELF 64-bit LSB shared object, x86-64, version
./configure --prefix=`pwd`/install --build=i386-linux
ac_cv_func_malloc_0_nonnull=yes --disable-udev --with-pic
I use this comand but the file is still 64bit
libusb-1.0.so.0.1.0: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
dynamically linked, BuildID[sha1]=0xae1d73381c0a5955801b5
