Xiaofan Chen wrote: > Take note now that libusbx/libusb will be merged Xiaofan, please hold off on reporting about the future until it has actually happened.
The behavior of just about everyone involved in the libusbx fork continues to blow my mind, but let's stay on topic. Of course writing about what you want and what you would like to see happen is perfectly legitimate, and indeed very valuable! Statements like "now that so-and-so said that such-and-such will happen" amplify expectations based on something that hasn't really happened yet. It can of course be helpful for libusb-1.0 API users to know the latest news from the hostile fork (their words) libusbx, but as I have always stated, and contrary to what libusbx developers communicate, I think there's really nothing more important than to maintain API compatibility as far as possible between forks, even if some new APIs make no sense. Finally, libusb-compat-0.1 is orthogonal both to libusb and libusbx. There are known issues with libusb-compat-0.1 on Windows, someone just needs to work on fixing them. That's certainly one way to help clean up the utter madness that is wannabe libusb implementations on Windows, so that users don't have to deal with so much confusion. //Peter ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
