-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Long story short, I've made an automatic generator for python_sdbus bluez bindings. I uploaded it to https://github.com/Kraken1121/bluez_sdbus_generator and the generated bindings module looks like this: https://github.com/Kraken1121/bluez_sdbus . It parses documentation in the provided bluez repository, extracts declarations and their corresponding documentation paragraphs, double checks the declarations against the declarations in the C files whenever possible (fun fact, this is how I've found a bug in bluez), and generate the interface classes (including original docstrings!). No offense, but I think the generated bindings look a lot better than your own bindings here
I think it works good enough for amateur usage and I think it has a good potential for anyone interested in maintaining a bluez bindings module: maintain the generated bindings module as the sdbus_bluez repository, run the generator against it whenever a new bluez version comes out, and just commit the difference if it looks good.
Unfortunately, I don't think I will be able to continue working on neither the generator nor the bindings. I'm not a bluetooth-related developer and I decided to write the parser just because it looked like an easy (haha) solution for one of my private projects. That project is complete, it works fine, and I don't think I'm interested in developing it any further, so I'm publishing the results of my work in hope you'll find the useful.
Feel free to ask any questions while I'm here