4 ms·

I don’t have a review, but here’s a significant project using it in a complicated cross platform build with different systems dependencies: https://github.com/r

by davemp 2y ago

I don’t have a review, but here’s a significant project using it in a complicated cross platform build with different systems dependencies: https://github.com/raysan5/raylib/blob/master/build.zig https://github.com/raysan5/raylib/blob/master/build.zig They also have a cmakelists.txt and pile of other cmake stuff to compare against: https://github.com/raysan5/raylib/tree/master/cmake https://github.com/raysan5/raylib/tree/master/cmake One of the nicer things is that if you’re working with less technical folks, they only need to download the zig binary because it bundles the entire toolchain. Real nice when on corporate windows systems.

einpoklum 2y ago
> they only need to download the zig binary because it bundles the entire toolchain. But that can't be possible... neither in principle nor in practice, because each projects needs a different toolchain. Different languages, different tools, different target platforms etc.
- davemp 2y ago
  Well it’s working in practice so I don’t really know what to tell you. > because each projects needs a different toolchain Not true. > Different languages I don’t think a caveat for C/C++/zig source files was needed… > Different tools If your project is unwilling/able to verify builds on anything except an ancient version of GCC that’s your project’s problem. In practice that’s a minority. > different target platforms Zig has 1st class cross compilation to all major platforms. If you’re using an embedded target you’ll need to vendor its linker script and boot code which is already the common practice. — I encourage you to try it before dismissing it.