Live data from Hacker News

Flipper Zero Zig Template

github.com

11–20 of 22 posts

Re: Flipper Zero Zig Template

#11
post #7
post #3

`@cImport` is dead, apparently, so the example should be updated.

Stop the misinformation, it’s just changing where it’s being done moving from the language to the build system itself: https://ziggit.dev/t/cimport-going-away/5132 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.

`@cImport` gets moved from the "mainline" language into a separate module -> this example won't compile on future versions of Zig, that's the point

Re: Flipper Zero Zig Template

#12
post #8

crazy that the readme doesn't link to the product. https://flipper.net/products/flipper-zero

downvoted to oblivion. huh. ok, let me give you a hint:

> 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/)

Re: Flipper Zero Zig Template

#13
post #3

`@cImport` is dead, apparently, so the example should be updated.

"No no he's not dead, he's, he's restin'!"

@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.

Re: Flipper Zero Zig Template

#15
post #12
post #8

crazy that the readme doesn't link to the product. https://flipper.net/products/flipper-zero

downvoted to oblivion. huh. ok, let me give you a hint: > 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…

Not everyone expects to appear on HN, but chasing links this is a par two golf course:

    UFBT: Unofficial Flipper Build Tool (installation guide)

    uFBT is a cross-platform tool for building applications for Flipper Zero.

Re: Flipper Zero Zig Template

#16
post #7
post #3

`@cImport` is dead, apparently, so the example should be updated.

Stop the misinformation, it’s just changing where it’s being done moving from the language to the build system itself: https://ziggit.dev/t/cimport-going-away/5132 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.

> Stop the misinformation

This was an unnecessary prelude to an otherwise helpful comment.

Re: Flipper Zero Zig Template

#19
post #12
post #8

crazy that the readme doesn't link to the product. https://flipper.net/products/flipper-zero

downvoted to oblivion. huh. ok, let me give you a hint: > 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…

I just updated the README :)

Re: Flipper Zero Zig Template

#20
post #13
post #3

`@cImport` is dead, apparently, so the example should be updated.

"No no he's not dead, he's, he's restin'!" @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 properl…

@cImport is dead. It's not moving anywhere, it's being deleted.

The build system allows you to expose C libraries as Zig modules that can be imported with the normal @import builtin.

Post reply on HN