@cImport is moving to the build system in an upcoming version (0.17, I think?). It's inconvenient, but it's unfortunately necessary.
The issue with @cImport is that when and the order the imports occur are almost impossible to define if you have multiple files and libraries. By moving it to the build system, the order now becomes deterministic and you can refer to it properly.
The build system allows you to expose C libraries as Zig modules that can be imported with the normal @import builtin.
It’s also decoupling Zig compiler and C compiler so they’re updated independently.
It’s still a bummer in my view as I just replaced my build pipelines with just a Zig compiler instead of emscripten but that’s fine.
This was an unnecessary prelude to an otherwise helpful comment.
> A modern, production-ready template for developing Flipper Zero applications using the Zig programming language. This project provides a streamlined build system that integrates Zig with the Flipper Zero SDK, enabling developers to write type-safe, memory-safe applications for the Flipper Zero platform.
replace "Flipper Zero" (the seventh and eighth words) in the first line with:
[Flipper Zero](https://flipper.net/) UFBT: Unofficial Flipper Build Tool (installation guide)
uFBT is a cross-platform tool for building applications for Flipper Zero.