C/C++ projects packaged for Zig

18 points by jcbhmr1 hour ago

3 comments

jeremyjh18 minutes ago
I just looked at one example...Wayland's meson.build is 142 LOC, but build.zig is 581.<p><a href="https://github.com/allyourcodebase/wayland/blob/master/build.zig" rel="nofollow">https://github.com/allyourcodebase/wayland/blob/master/build...</a> <a href="https://github.com/wayland-mirror/wayland/blob/main/meson.build" rel="nofollow">https://github.com/wayland-mirror/wayland/blob/main/meson.bu...</a>
- gregdaniels4214 minutes ago
  The Zig is far more explicit about what it is doing with lots of very long dotted commands for specifiy version headers and such, so maybe not super fair unless you like magic.
rtpg31 minutes ago
I'm a bit worried this is intro'ing the classic problem we have in Bazel land, where everyone is having to show up with their own sort of packaging scripts etc instead of using upstream tooling one way or another.<p>I had the impression `zig` already has stuff like `zig cc`. Would... would `zig make` be an impossible proposition? Maybe that makes no sense.
- LoganDark15 minutes ago
  When I build software to use on my personal machine, I usually swap the build system out for tup. Maintainers never see this, but tup is just better for me. (Exception: Rust projects that use cargo, and JS projects that use bundling)
gracefulliberty1 hour ago
Both an excellent showcase of the Zig build system and a convenient way to use C libraries within Zig.