Libtool versioning should in particular work for cross platform applications,
and I have used it a lot for that purpose myself. But admittedly never with
Windows, which is unfortunately behaving very differently when it comes to
shared libraries compared to POSIX systems. So in some sense I am n
I appreciate that merging is incomplete and still requires a lot of work.
But my complaint is that this is highly intransparent, and the result is
confusing to outsiders. Indeed, except for that email I dug out from a mailing
list archive, there is no explicit hint that the libusb and libusbx pr
I just discovered that libusb and libusbx merged. That is, what I did notice
was that the download link on http://www.libusb.org/ suddenly is pointing to
libusbx... but it wasn't quite clear if that was done in good faith or rather a
hostile takeover (see also the terrible ffmpeg vs. libav saga)
This pull request update the libtool versioning data in configure.ac for the
libusb shared library.
There is a nice comment in your configure.ac that explains how to properly do
this, unfortunately, it seems this has been ignored: Many new APIs have been
added to libusb and old ones extended, w
