التصريح عن الملفات التنفيذية والمكتبات

The things you compile are called artifacts: an executable you run, or a library other code links against. You declare them in build.zig. 📦

Create a runnable program with addExecutable. You give it a name and the root source file that holds main.

The artifact needs a root_module built from your main file, plus the target and optimize values you chose earlier.

That module also takes the target and optimize fields, so the executable honors whatever the command line requested.

Creating an exe is not enough; tell Zig to place it in zig-out with installArtifact so the default build emits it.

Installed binaries appear under zig-out/bin by convention. Run zig build and look there for your freshly compiled program.

For reusable code, use addLibrary instead. It produces a library artifact others can import and link against.

A library can be static (baked into the caller) or dynamic (a shared file). You set linkage when you declare the library.

Connect them so the exe can call the library's code: use linkLibrary to add the dependency edge.

If your code calls C standard functions, request libc on the artifact with linkLibC so the right system library is linked.

Each artifact is a node; linking adds edges. Together they form the build graph Zig walks when you run the build. ✅

Recall which call actually emits a built binary into zig-out.

You declared artifacts with addExecutable and addLibrary, set their root module and target, then used installArtifact and linkLibrary to wire them. 🎯