2010/4/8 Xiaofan Chen <xiaof...@gmail.com>: > On Thu, Apr 8, 2010 at 9:38 PM, Wander Lairson <wander.lair...@gmail.com> > wrote: >> libusb-1.0 for mingw feels like was built with cdecl calling >> convention. When I load it with WinDLL (stdcall), it fails, but >> loading it with CDLL (cdecl), it works fine: >> >> Just wondering if cdecl calling convention for mingw is right... If it >> is, I must manage libusb10 backend to detect it is loading a mingw lib >> and apply cdecl calling convention. >> > > Ah, this may be the case. I need to ask again in the libusb mailing > list. The MSVC solution generates stdcall. And I believe if they > are different, then Pete will need to change the MinGW/Cygwin > build to use stdcall.
OK. > > Are you using the binary snapshots from the libusb website? > http://www.libusb.org/wiki/windows_backend Yes, I am. > > > -- > Xiaofan http://mcuee.blogspot.com > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > pyusb-users mailing list > pyusb-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/pyusb-users > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ pyusb-users mailing list pyusb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pyusb-users
