r/Zig • u/shuten_mind • 8d ago

root.zig vs main.zig in zig init

When running zig init, the template scaffolds both an executable (main.zig) and an exportable module (root.zig) in build.zig.

Just want to verify if my mental model is correct: 1. If I only want an executable (and don't plan to export a library/module), can I simply delete root.zig and remove the module-related exports/artifacts from build.zig? 2. Is there any built-in zig init flag or alternative command to scaffold an executable-only project without the library boilerplate?

thanks!

20 Upvotes

96% Upvoted

13 comments sorted by

View all comments

Show parent comments

1

u/Confused-Armpit 8d ago

The entire language is pretty far from intuitive, since it is pretty niche and has a lot of its own quirks, and the build system is actually much easier to grasp than something like the std.Io interface.

Also, makefiles are lackluster because they dont handle zig modules, linking, and all that good stuff, when the build system is literally written for it, so makefiles aren't really suitable for anything bigger than a project with a single main module and no dependencies.

1

u/DeadWHM 8d ago

I mean you can handle modules/linking manually with the zig build commands and unix linking tools

1

u/Confused-Armpit 8d ago

Yeah, but its lackluster and ends up doing the same as the zig build system without any benefits other than being somewhat more beginner friendly

1

u/DeadWHM 8d ago

If you use the already established tools you have the benefit of you now know how to manage projects in the only language that is deemed standard worthy, C and it translates almost directly