zig-vulkan-triangle VS zig

I get the same error when I try to build zig-vulkan-triangle, zang, and ichigo on 0.7.x, and even if I zig cc test.c -lSDL2 -lvulkan (test.c is just int main(int argc, char* argv[]) { return 0; }). This builds fine when I switch back to Zig 0.6.0 or use the system-installed clang (6.0.0-1ubuntu2) or gcc (7.5.0-3ubuntu1~18.04). Stranger still, 0.7.x works fine with -lc and -lm, but not any of the other libraries I tried. Does this perhaps have something to do with Zig building its own libc? I also tried zig cc test.c -target x86_64-linux-musl -lSDL2 with the same results.

There is an issue proposing this approach: https://github.com/ziglang/zig/issues/4284

https://github.com/ziglang/zig/issues/224

e.g.:

> > When debugging/prototyping, it's useful to comment out a line without having to refactor, e.g.

When writing code in a scripting language, sometimes you need that extra bit of performance (or maybe an async feature from Zig).

NodeJS is by no means a slow runtime, it wouldn’t be so popular if it was. But compared to Bun, it’s slow. Bun was built from the ground up with speed in mind, using both JavascriptCore and Zig. The Bun team spent an enormous amount of time and energy trying to make Bun fast, including lots of profiling, benchmarking, and optimizations.

ntdll.dll!RtlUserThreadStart()

There are valid reasons to use APIs from NTDLL. Where I disagree with zig#1840 is the idea that it is always better to use NTDLL versions of API. Every other software ecosystem uses the standard Win32 APIs and diverging from that without a good reason seems like a good way to have unexpected behavior. One concrete example is most users and programmers expect Windows to redirect some file system paths when running on WOW64. But this is implemented in Kernel32, not ntdll.

https://github.com/ziglang/zig/issues/11894

Zig also has an IRC channel on libera (#zig) that is moderated by Andrew Kelley.[1]

[1] https://github.com/ziglang/zig/wiki/Community