Open alexdupre opened 6 years ago
I've pending to drop the dependency on libusb in favor of the internal libusb due to extra functionality implemented in the bundled version.
Note that - at least according to what @reillyeon wrote me some time ago - Chrome is planning to switch away from libusb and write their own backends from scratch. (Seeing what mess windows libusb is, it is maybe a good idea.)
The in-tree copy of libusb is rather old so for FreeBSD support you probably want to be using the version from the system.
At some point Chrome will no longer use libusb on macOS and Windows. It already is no longer used on Android, Chrome OS and Linux.
I recommend that FreeBSD maintainers either build a new backend in Chromium that uses FreeBSD's libusb20 library or be aware that at some point the existing libusb backend will be removed and they will need to fork and maintain it themselves.
USB devices are present and with correct permissions, but Chrome WebUSB API implementation cannot find anything.