This post seems to be missing an additional opportunity: Zig's build can involve go build! Use Build.addSystemCommand, have it depend on library step, and have the install step depend on that step. This reduces the steps to build to just 'zig build'
My biggest problem with “zig build” is learning it. Mainly because it still changes from version to version, and having a clear picture of what steps are and how they interact is somehow hard for me.
Obviously I will overcome this, but unlike zig itself, the build file still feels like guesswork to me.
The generated html docs can also be hard to read / understand. Zig 0.14.0 changed something about LazyPath (I think that‘s how it‘s called) and I had a hard time figuring out how to migrate.
laserbeam|11 months ago
Obviously I will overcome this, but unlike zig itself, the build file still feels like guesswork to me.
danhau|11 months ago
The generated html docs can also be hard to read / understand. Zig 0.14.0 changed something about LazyPath (I think that‘s how it‘s called) and I had a hard time figuring out how to migrate.
silisili|11 months ago
jcalabro|11 months ago