Kustaa Nyholm wrote: > I can only speak for myself but I do not see it likely > that libusbx 1.x (or libusb for that matter) will go out > of its way to break neither the ABI or API in the future.
This is true at least for libusb. > (As a side note and mostly commercial software developer > actually responsible for making things work, I must say > I'm in favor of always bundling , dynamically or staticaly, > your libraries with your application, especially small ones > like libusb, that is the only way to ensure compatibility, > none of your shared library hell than you. On Windows and Mac OS X I agree with you and Orin, because there are few (no?) useful system-wide package managers. On Linux and BSD there is generally a reliable package manager which handles dependencies, thus avoiding the problem. I of course understand that you may not have the luxury of working primarily with those platforms, and the library is intended to be portable, so I think it's a good point to make. Thanks! //Peter ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
