On 17/05/2011 17:38, Chris Frey wrote: > 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. Ah, that makes sense. Is this the interface that BBDevMgr.exe exposes via a COM object? The one described by: http://docs.blackberry.com/en/developers/deliverables/1093/Desktop_API_Reference_Guide_46.pdf
> 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. Is there any way to build this Barry without low level USB support? Or is it just a future possibility that you want to make easier by organising the code in such a way? > 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. Ok. I'll probably rename the define to something about low level USB support to make it clearer if Barry is ever ported to platforms without libusb. > Let me know if this explanation is not clear enough :-) > Nope, that's good enough for me, thanks. Regards, Toby ------------------------------------------------------------------------------ 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
