How can it be updated to Flipper API v0.71?

[unrealsolver]

[dcoles]

Hi @unrealsolver,

The current 0.4.1 release should support SDK version 7.5 ([email protected]).

Let me know if you're running into an issue on that version of the firmware.

[unrealsolver]

I mean, how can I specify which firmare to use? I grep'd through the code base, but there are no explicit versions mentioned (like "0.68") or any scripts/external dependecies, which download flipperzero-firmware from github. So I don't really understand how does flipperzero-rs is connected to appropriate version of flipperzero-firmware.

[dcoles]

The way I currently handle this is to use generate-bindings (e.g. 9daed09) to regenerate bindings.rs when the SDK becomes incompatible. It uses bindgen internally.

You can see the latest supported SDK version on flipperzero-sys, but I'll see if I can make it more visible in the README/documentation.

The reason I take this approach, rather than using a build.rs script is that currently the Flipper Zero SDK changes almost every release. You wouldn't be able to reliably build bindings without pinning it to a specific flipperzero-firmware release and it would add a build-time dependency on flipperzero-firmware and its toolchain.

If you ever notice that it's out of date, feel free to open an issue and I'll happily tag a new release.

[unrealsolver]

Does this process require manual labour? Or it could be just run script and build process? Because it might be simpler to set some env var (like in the example) and regenerate bindings automatically.

[dcoles]

Unfortunately, yes. I have typically needed to make non-trivial changes to generate-bindings to support each release.

Additionally, the external application SDK has broken backwards compatibility several times.
As an example, the 0.71.1 release has SDK version 7.5, while the 0.73.1 release has SDK version 10.1.

This means that any crate directly depending on flipperzero-sys (including flipperzero and flipperzero-rt) will likely need code changes to handle the API breakage.

[GitCat3]

yeah I just got the api mismatch error on my dev firmware, is it only updated to release?

[GitCat3]

one last thing, what is the sdk.opts file?

[GitCat3]

I think I am confused on where to put the files. I have a flipperzero firmware that I have ran ./fbt on already, which folder do I need to clone this project to in order to generate bindings?

[dcoles]

After running ./fbt in the flipper-firmware directory, there should now be be a build/f7-firmware-D/sdk/ directory.

The sdk.opts file in this folder give the path of important directories and the compiler flags that bindgen needs to use.

After running generate-bindings ${FLIPPERZERO_FIRMWARE}/build/f7-firmware-D/sdk/, there should be a new bindings.rs in the current directory. You can then use this to replace the one in crates/sys/src/.

[GitCat3]

So in order to do that would I run the cargo run with the arguments that you showed?

[dcoles]

Yes. This was the command I used:

cd flipperzero-rs/tools
cargo run --bin generate-bindings ../../flipperzero-firmware/build/f7-firmware-D/sdk