| commit | 8defc5bf9518c172e02cab9a7b7539178d90d2c1 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Wed Dec 04 00:12:59 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Wed Dec 04 00:12:59 2024 +0000 |
| tree | c19333eb03952cc2a09f98f975727b84e5d6e296 | |
| parent | f86e48be1626d9222b8212b34fb53abcab1d6307 [diff] | |
| parent | 74c0a56fa5f8d980dbebb1c6a473b0b47cf10326 [diff] |
Snap for 12742097 from 74c0a56fa5f8d980dbebb1c6a473b0b47cf10326 to 25Q1-release Change-Id: Ib923633ae28cbfc0c76b71d3df378dba90d496ed
This crate provides a safe wrapper around the native libusb library. It applies the RAII pattern and Rust lifetimes to ensure safe usage of all libusb functionality. The RAII pattern ensures that all acquired resources are released when they're no longer needed, and Rust lifetimes ensure that resources are released in a proper order.
To use rusb no extra setup is required as rusb will automatically download the source for libusb and build it.
However if building libusb fails you can also try setting up the native libusb library where it can be found by pkg-config or vcpkg.
All systems supported by the native libusb library are also supported by the libusb crate. It's been tested on Linux, OS X, and Windows.
The rusb crate can be used when cross-compiling to a foreign target. Details on how to cross-compile rusb are explained in the libusb1-sys crate's README.
Add rusb as a dependency in Cargo.toml:
[dependencies] rusb = "0.9"
Import the rusb crate. The starting point for nearly all rusb functionality is to create a context object. With a context object, you can list devices, read their descriptors, open them, and communicate with their endpoints:
fn main() { for device in rusb::devices().unwrap().iter() { let device_desc = device.device_descriptor().unwrap(); println!("Bus {:03} Device {:03} ID {:04x}:{:04x}", device.bus_number(), device.address(), device_desc.vendor_id(), device_desc.product_id()); } }
Distributed under the MIT License.
If you link native libusb (by example using vendored features) library statically then you must follow GNU LGPL from libusb.