On 2012.09.26 23:55, Pete Batard wrote: > I'll try to dig up the old issue when I have a chance (unless someone > can beat me to it).
This issue might be slightly different than the previous one, though I expect the proposed changes for the 2.0 API to fix it. Basically, the old issue we got with interface was MS specific, and had to do with the inclusion of headers that may define an interface macro. As a matter of fact, we have a a comment regarding this at line 60 of our header: https://github.com/libusbx/libusbx/blob/master/libusb/libusb.h#L60 Is there a chance that the issue is not with g++ but with an interface macro defined in one of the headers included before libusb.h? Especially, are you compiling with g++ on Windows or on an different platform? Regards, /Pete ------------------------------------------------------------------------------ How fast is your code? 3 out of 4 devs don\\\'t know how their code performs in production. Find out how slow your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219672;13503038;z? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
