Embedded bindings generate different bindings depending on the target board.

[jkoking]

I forked rust4pebble because the original author never finished the bindings and it no longer works with the new Pebble CLI I feel like the original author took the wrong approach to the binding generation. The Pebble SDK is split into six different sets of header files. The Pebble CLI then builds your project multiple times depending on which watches you want to support. The original author set the project up to generate the bindings based on a cargo argument telling it which watch the binary should be generated for. My concern is that this would make it difficult to debug higher level code because you would need to rebuild the code six times every time you wanted to test. I would separate each watch into its own sys crate and define which watches you are trying to build for using feature flags, but I'm new to bindgen. So I wanted to ask people who were more experienced for their opinions. If you think I'm wrong about anything mentioned here, please let me know.