Issues found with existing distfiles:
distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip
distfiles/fortran-utils-1.1.tar.gz
distfiles/ivykis-0.39.tar.gz
distfiles/enum-1.11.tar.gz
distfiles/pvs-3.2-libraries.tgz
distfiles/pvs-3.2-linux.tgz
distfiles/pvs-3.2-solaris.tgz
distfiles/pvs-3.2-system.tgz
No changes made to these distinfo files.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
---------------------
Date: Mon May 20 17:34:02 2013 -0600
libusb-compat-0.1.5
Date: Mon May 20 17:33:43 2013 -0600
Add bootstrap.sh and do not set debug mode by default.
Date: Mon May 20 17:32:43 2013 -0600
Replace the deprecated INCLUDES token with AM_CPPFLAGS in Makefile.am
Date: Fri Aug 24 17:13:11 2012 -0400
libusb.pc.in: Add missing Requires.private: libusb-1.0 so that
pkg-config adds the libusb 1.0 library and dependencies when
static linking.
Date: Thu Apr 4 10:53:42 2013 -0600
use atexit() to call libusb_exit()
Fixes#130
Date: Thu Apr 4 10:53:01 2013 -0600
fix autoconf errors/warnings
Fixes#161
Date: Sun May 13 19:50:38 2012 +0800
examples: Link only with ../libusb/libusb.la and not with -lusb
Similar to libusb.git commit 93b0e09d53ed1d177631af9182378492481a790a
http://git.libusb.org/?p=libusb.git;a=commitdiff;h=93b0e09d53ed1d177631af918
Previous _LDFLAGS included both the freshly built libusb in ../libusb
and -lusb, where libtool would usually resolve the latter to an
already-installed libusb library in the system. The extra reference
to a second libusb library may cause failures to build examples
on some platforms and is wrong.
Fixes#135.
Notes: depends on libusbx (we need a switch between the two)
Conflicts with libusb (we need a switch between the two)
libusb-compat-0.1 is a replacement for libusb-0.1. However, instead
of being an actual implementation, libusb-0.1 is more of a
compatibility layer (or wrapper) which just converts libusb-0.1
calls into their libusb-1.0 equivalents.
It aims to look, feel and behave exactly like libusb-0.1. As it is
a replacement, you cannot install it alongside libusb-0.1 on the
same system.
As the compatibility layer implements the exact same ABI and API,
no modifications to existing libusb-0.1-based applications are
needed. You do not even have to recompile them. This compatibility
layer is a drop-in replacement.
