6/1/2026 at 2:46:25 PM
`@cImport` is dead, apparently, so the example should be updated.by bpavuk
6/2/2026 at 1:09:05 AM
"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.
by bsder
6/1/2026 at 6:43:03 PM
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/5132It’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.
by speps
6/1/2026 at 11:20:09 PM
`@cImport` gets moved from the "mainline" language into a separate module -> this example won't compile on future versions of Zig, that's the pointby bpavuk
6/1/2026 at 6:06:53 PM
Deprecatedby teddyX
6/1/2026 at 2:58:46 PM
It's deprecated not removed yet.by Narew
6/1/2026 at 3:22:03 PM
I'm a little too lazy to double-check, but either way 0.17.0 is around the corner, where it will totally get nixedby bpavuk
6/1/2026 at 8:23:47 PM
It is being moved not going away.It is just a wrapper around zig translate-c, moving it to the build system moves the resulting clang dependency to a place where it can be optional.
The functionality is staying, it is just moving.
by nyrikki
6/1/2026 at 10:36:42 PM
The point here is that these examples need to be updated because @cImport, the syntactic feature of Zig, is being deprecated and removed. That there exists an alternative isn't relevant.by Conscat