On Tue, May 17, 2011 at 04:48:04PM +0100, Toby Gray wrote: > What other USB libraries does Barry currently supports other than libusb > 0.1? Is one of them native Windows APIs? > > Or is it ok if I tidy up this code and split it into suitable interfaces > and just supply libusb 0.1 and libusb 1.0 implementations of them?
Hi Toby, The other "usb interface" is not a pure USB interface at all, but the RIM driver that comes with Windows. They provide a low level mechanism that supplies the functionality of socket.cc, packet.cc, etc. I had hoped that maybe Barry could support this, but I'm not sure if the RIM software license will allow it. Until then, I want to keep the ability to turn off low level USB support. This is only needed if we have to implement our own socket and packet functionality. Feel free to add your libusb 1.0 / 0.1 switching logic inside USB_LIBUSB blocks. You can do this once, if possible, and put this in other headers. Let me know if this explanation is not clear enough :-) Thanks, - Chris ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
