from 0.0.9, also remove libusb recipe (see below)
changes:
- remove some unnecessary logics derived from libusb-0.1
- now PROVIDES libusb
- bluez4 depends on libusb instead of libusb-compat
libusb-0.1 vs. libusb-compat
libusb-compat is intended to be a drop-in replacement of libusb-0.1,
building on top of libusb-1.0 (which has different API from -0.1).
Few known packages don't work with libusb-compat, notable example
is libmtp. Since most packages work very well with libusb-compat,
and libusb-compat doesn't suffer from power consumption issue of
libusb-0.1 (which is often very important for embedded systems),
drop libusb-0.1 and move to libusb-compat completely. If we see
any problems in the future, either the package should be fixed
or we can add back libusb-0.1 as needed.
Signed-off-by: Qing He <qing.he@intel.com>
from 0.9.2
changes:
- the previous recipe was derived from libusb-0.1 and thus had many
inconsistencies, e.g. binconfig and lib_packages are not necessary,
libusb1 doesn't provide libusb++, etc. Remove these legacies
- remove the patch 0.9.0-gcc3.4-compat-fix
Signed-off-by: Qing He <qing.he@intel.com>
update homepage
change license to reflect GPL|BSD dual licensing of the header
update description to reflect the legacy version
change to use new patch parameter
Signed-off-by: Qing He <qing.he@intel.com>
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
Move the functionality into autotools and ensure all our Poky recipes are no
longer using it.
Keep the autools_stage class around for OE compatability but just have it
inherit autools.
Signed-off-by: Joshua Lock <josh@linux.intel.com>
Qing He
Joshua Lock
Richard Purdie
Richard Purdie
Richard Purdie
Marcin Juszkiewicz
Chris Lord