#linux-bluetooth #bluetooth #bluez #dbus #ble #generated-bindings #linux

bluez-generated

Generated async D-Bus bindings for talking to BlueZ on Linux

4 releases (2 breaking)

0.3.0 Jan 18, 2023
0.2.1 Jan 8, 2021
0.2.0 Oct 30, 2020
0.1.0 Oct 18, 2020

#866 in Unix APIs

Download history 2659/week @ 2024-08-14 2271/week @ 2024-08-21 3097/week @ 2024-08-28 3008/week @ 2024-09-04 3011/week @ 2024-09-11 2971/week @ 2024-09-18 2857/week @ 2024-09-25 2783/week @ 2024-10-02 2928/week @ 2024-10-09 3641/week @ 2024-10-16 2730/week @ 2024-10-23 2782/week @ 2024-10-30 2607/week @ 2024-11-06 2441/week @ 2024-11-13 2700/week @ 2024-11-20 2275/week @ 2024-11-27

10,437 downloads per month
Used in 63 crates (via bluez-async)

MIT/Apache

59KB
1.5K SLoC

Generated bindings for BlueZ

crates.io page docs.rs page

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.

Dependencies

~6MB
~128K SLoC