bluez-generated
| Crates.io | bluez-generated |
| lib.rs | bluez-generated |
| version | |
| source | src |
| created_at | 2020-10-18 20:11:48.175828 |
| updated_at | 2024-12-12 18:35:03.496404 |
| description | Generated async D-Bus bindings for talking to BlueZ on Linux. |
| homepage | |
| repository | https://github.com/bluez-rs/bluez-async/ |
| max_upload_size | |
| id | 302402 |
| Cargo.toml error: | TOML parse error at line 21, column 1 | 21 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
David Laban (alsuren)
documentation
README
Generated bindings for BlueZ
Generated async D-Bus bindings for talking to BlueZ on Linux.
Bindings are generated from introspection data, using
dbus-codegen. This means that it is relatively easy to
maintain, but it only covers interfaces that I have the devices for.
Adding Interfaces
If there is an interface that you need which is not generated, it should be reasonably straightforward to generate them and send a pull request. See introspect.sh for details. It's also perfectly reasonable to generate the interfaces you need and vendor them into your project.
Future Direction
Only async bindings are generated. Blocking bindings could also be generated, but I'm unlikely to use them, so they would need to be contributed by someone else.
It would be nice to generate some strongly typed bindings around add_match() for subscribing to
PropertiesChanged signals as as stream for a particular property.
License
Licensed under either of
at your option.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.