News for hackers. Stuff that matters.
Re:Building Statically Linked Go Executables with CGO and Zig by Laremere on Friday March 28, 2025 @01:59PM (#43508287)
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'
Re:Building Statically Linked Go Executables with CGO and Zig by jcalabro on Friday March 28, 2025 @02:07PM (#43508374)
zigception!
Re:Building Statically Linked Go Executables with CGO and Zig by silisili on Friday March 28, 2025 @04:52PM (#43509710)
Do you by chance have a link to a working example of this? Sounds interesting...
Re:Building Statically Linked Go Executables with CGO and Zig by laserbeam on Saturday March 29, 2025 @12:42AM (#43512799)
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.

Re:Building Statically Linked Go Executables with CGO and Zig by danhau on Saturday March 29, 2025 @12:27PM (#43516660)
That‘s my experience as well.

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.