zig build: separate the maker process from the configurer process #35428

Merged

andrewrk merged 179 commits from build-runner-process into master 2026-05-26 18:00:45 +02:00

Conversation 4 Commits 179 Files changed 99 +16343 -9994

andrewrk commented 2026-05-23 10:01:18 +02:00

Owner

Copy link

closes #31397
closes #31691

Release Notes

The primary motivation is to make zig build faster, both in the sense that it will take less time to compile, because only the user's build.zig logic is being recompiled when it changes, and in the sense that the build runner is built with optimizations enabled, which is starting to become more valuable now that we have introduced --watch and --fuzz. Furthermore, the build.zig logic can be skipped sometimes depending on what CLI flags are used with zig build.

This changeset heavily reworks the internal mechanism of the zig build system, however, it is mostly non-breaking from an API perspective, with the exceptions noted below.

Third-party tooling such as ZLS will benefit from consuming the serialized configuration file rather than maintaining a fork of the build runner.

New CLI Arguments

  --maker-opt=[mode]           Change maker executable optimization mode (default: ReleaseSafe)

--print-configuration        Render configuration as .zon to stdout

Run Step: Passthru Args

In the Run step, passthru args are all together now, not observable in
configure phase whether run args are provided.

if (b.args) |args| {
    run_cmd.addArgs(args);
}

⬇️

run_cmd.addPassthruArgs();

This removes a capability from build scripts since they can no longer observe
those arguments. In exchange, it means that when changing those arguments,
build scripts no longer must be rebuilt from source.

Fmt Step: Options

paths and exclude_paths are now LazyPath lists. There is a convenience method to create them: b.pathList.

-    const fmt_include_paths = &.{ "lib", "src", "test", "tools", "build.zig", "build.zig.zon" };
-    const fmt_exclude_paths = &.{ "test/cases", "test/behavior/zon" };
+    const fmt_include_paths = b.pathList(&.{ "lib", "src", "test", "tools", "build.zig", "build.zig.zon" });
+    const fmt_exclude_paths = b.pathList(&.{ "test/cases", "test/behavior/zon" });

std.Build API

• b.build_root (Directory) -> b.root (Path)
• ConfigHeader.Options: include_guard_override -> include_guard
• LazyPath: getDisplayName -> format ("{f}")
• LazyPath.basename: removed since the value is not known until make phase
• b.findProgram divided into findProgram and findProgramLazy and API future-proofed.
• ConfigHeader now properly reports unused values for all styles

std.Target API

• parseCpuModel now returns optional rather than error

Build System Behavior

• When targeting Windows or Wine, artifact args added to Run steps used to modify PATH based on the set of directories containing the recursive set of DLL dependencies. Now this is only done for argv[0]. The motivation for also doing this for the other command line arguments is unclear, since those DLLs don't need to be loaded in order to execute argv[0].

Perf Data Point: zig build -h (cached)

Benchmark 1 (34 runs): master/zig build -h
  measurement          mean ± σ            min … max           outliers         delta
  wall_time           150ms ± 5.52ms     145ms …  165ms          4 (12%)        0%
  peak_rss           84.8MB ±  275KB    84.2MB … 85.1MB          0 ( 0%)        0%
  cpu_cycles          593M  ± 4.01M      588M  …  608M           2 ( 6%)        0%
  instructions        995M  ± 52.5K      995M  …  995M           0 ( 0%)        0%
  cache_references   25.8M  ±  165K     25.4M  … 26.1M           0 ( 0%)        0%
  cache_misses        651K  ± 20.1K      619K  …  697K           0 ( 0%)        0%
  branch_misses       918K  ± 7.44K      906K  …  935K           0 ( 0%)        0%
Benchmark 2 (348 runs): branch/zig build -h
  measurement          mean ± σ            min … max           outliers         delta
  wall_time          14.3ms ±  744us    13.2ms … 23.3ms          8 ( 2%)        ⚡- 90.4% ±  0.4%
  peak_rss           78.5MB ±  562KB    77.1MB … 81.4MB          7 ( 2%)        ⚡-  7.4% ±  0.2%
  cpu_cycles         24.1M  ±  821K     22.8M  … 27.1M           3 ( 1%)        ⚡- 95.9% ±  0.1%
  instructions       43.7M  ± 23.8K     43.7M  … 43.8M          56 (16%)        ⚡- 95.6% ±  0.0%
  cache_references   1.46M  ± 14.6K     1.40M  … 1.50M          19 ( 5%)        ⚡- 94.3% ±  0.1%
  cache_misses        142K  ± 4.87K      127K  …  157K           2 ( 1%)        ⚡- 78.1% ±  0.4%
  branch_misses       126K  ± 1.37K      120K  …  129K          12 ( 3%)        ⚡- 86.3% ±  0.1%

Perf Data Point: Running a subset of the toolchain test suite

Fresh cache except in both cases I let the build runner / maker / configurer
get cached beforehand.

master:

$ time -v stage3/bin/zig build test-cases test-standalone -Dskip-release --seed 0
        Elapsed (wall clock) time (h:mm:ss or m:ss): 2:09.93
        Maximum resident set size (kbytes): 496512

branch:

$ time -v stage3/bin/zig build test-cases test-standalone -Dskip-release --seed 0 --maker-opt=ReleaseFast
        Elapsed (wall clock) time (h:mm:ss or m:ss): 1:46.88
        Maximum resident set size (kbytes): 495700

It's only one data point, but the new thing is faster and less memory. As is
expected from being compiled in optimized mode. That's the point of the
changeset.

Introduce the Concept of Configure Cache Poisoning

If the cache is poisoned means that the configure logic had side
effects, or otherwise did something that could not be tracked by the
cache system.

This is not to be confused with whether individual steps may have side
effects when being evaluated; it has to do with the logic inside build.zig
itself. For example, a Run step that prints "hello world" has side
effects at make time and therefore does not warrant setting this flag,
while checking for the existence of scdoc at configure time in order to
choose the default value for a configuration option does.

Keeping the cache pure will make zig build faster, bypassing the
configurer process when identical configuration would be generated.

When the cache is poisoned, the maker process will delete the build
configuration file upon ingesting it since it cannot be reused.

Currently the only way to poison the cache is to call findProgram.

Advanced users can override the cache poisoning behavior with a CLI option:

  --cache-poison[=mode]        Override configuration caching behavior
      pure                     (default) Avoid false positive cache hits
      poisoned                 Don't cache the configuration
      disallowed               Panics when cache would be poisoned
      ignored                  A little poison never hurt anybody

findProgram

Immediately (in the configure phase), searches for an executable on the host
that has more than one possible name.

Names are searched in order, observing search prefixes first and then PATH
environment variable.

Calling this function poisons the configuration cache, so it is only
appropriate when the existence of the program or its output needs to be
observed by configuration logic. That's why there is a lazy variant of this function now.

findProgramLazy

Creates an anonymous Step that searches for an executable on the host that
has more than one possible name.

Returns the LazyPath of the found executable. The search only takes place
if the LazyPath will be used by a depending Step.

This API is useful in the following cases:

• The binary is not named the same across all systems (for example "python"
  vs "python3").
• The binary may be produced by building from source rather than being
  globally installed and will therefore be possibly found in one of the
  search prefix paths.

Removed Ability to Override Build Runner

There is no concept of a "build runner" any more; it has been split in two:
configurer and maker.

Users of this feature will likely want to no longer override any logic, and
instead consume the configuration file produced by configurer.

If overriding one or the other of these is desired, the feature will need to be
re-introduced (as --override-maker or --override-configurer).

Followup Issues

• CLI flag to print path to the configuration file
• test a bunch of third party projects / help people migrate
• search prefixes added at configuration time should be package-local
• introduce the concept of adding path dependencies of the configure script itself
  • don't forget to implement Cache.addPathPost and Configuration.Path.toCachePath
  • make --watch rerun itself
• Maker.WebServer: fix bad logic in serveTarFile
• Maker.WebServer: don't do linear search in the steps array
• maker: refactor and reuse the fuzz number parsing here (--maxrss, --debounce)
• handle missing cache hits when chaining two run steps
• Absolute and cwd-relative paths in build cache
• build system fmt step with check=false does not acquire a write lock on source files
• enhance CheckFile step output when there is not a match
• stop leaking into global process arena. audit all uses of graph.arena
• reduce the size of Maker.Step.Extended (make Run smaller) probably by using an arena per make
• consider using ReleaseFast by default for Maker
• make the generated dependencies.zig be dependencies.zon and don't put absolute paths in there
  • and adjust dependencyInner to not openDir()
• make more stuff use IndexType
• make addExtra return Index using reflection
• refactor with DefaultingEnum
• get the target from the parent process instead
• link_eh_frame_hdr should be DefaultingBool
• make --foo, --no-foo CLI args uniform (make them -f args instead)
• install steps should provide generated files for installed things, then delete the run step hack
  • but artifact install steps also add paths for dyn libs on windows
• no more "artifact arg" to run step. if you want to run the post-install binary, get the lazy path
  from the install step.
• UpdateSourceFiles: introduce Group
• WriteFiles: introduce Group
• re-examine the use case of adding file paths to Options steps
• extract the reusable Configure abstractions and reuse it for Zir etc
• add the ability to delete files to UpdateSourceFiles
• merge the code of Maker.Step.Compile.checkCompileErrors with std.testing.expectEqualStrings
• std.Build.Run: make addPathDir use LazyPath. This will require enhancing the env_map to support
  some values being strings and some values being LazyPaths.
  • also this is not the appropriate place to integrate with wine. move it to Maker logic
• constrain the set of environment variables passed to configurer. they can ask for more but they
  will integrate properly with the cache system.
• should ConfigHeader run in configurer and store the rendered string?
• ConfigHeader:
  • TODO: use C-specific escaping instead of zig string literals
  • TODO: use nasm-specific escaping instead of zig string literals
• enhance doctest to use "--listen=-" rather than operating in a temporary directory
• Maker: eliminate memory allocation in the hot path (search for "TODO eliminate memory allocation here" x2)
• print more stuff in --print-configuration
  • paths
  • unlazy deps
  • system integrations
  • available options
• Maker.Step.InstallDir: update the call to truncatePath to first check dest
  stat. if already exists and length zero, skip the open() call and track the
  "all_cached" flag properly like the surrounding code.
• Maker.Step.Run: when trying to interpret, learn the target from the binary
  directly rather than from relying on it being a Compile step. This will make
  this logic work even for the edge case that the binary was produced by a
  third party.
• investigate why configurer takes so long to compile
• fmt step: import zig fmt code directly rather than child proc?
• add zig reduce functionality directly into the build system. detect when the compiler crashes and
  offer a command that will attempt to make a reproducer.

closes #31397 closes #31691 ## Release Notes The primary motivation is to make `zig build` faster, both in the sense that it will take less time to compile, because only the user's `build.zig` logic is being recompiled when it changes, and in the sense that the build runner is built with optimizations enabled, which is starting to become more valuable now that we have introduced `--watch` and `--fuzz`. Furthermore, the build.zig logic can be skipped sometimes depending on what CLI flags are used with `zig build`. This changeset heavily reworks the internal mechanism of the zig build system, however, it is mostly non-breaking from an API perspective, with the exceptions noted below. Third-party tooling such as ZLS will benefit from consuming the serialized configuration file rather than maintaining a fork of the build runner. ### New CLI Arguments ``` --maker-opt=[mode] Change maker executable optimization mode (default: ReleaseSafe) ``` ``` --print-configuration Render configuration as .zon to stdout ``` ### Run Step: Passthru Args In the Run step, passthru args are all together now, not observable in configure phase whether run args are provided. ```zig if (b.args) |args| { run_cmd.addArgs(args); } ``` ⬇️ ```zig run_cmd.addPassthruArgs(); ``` This removes a capability from build scripts since they can no longer observe those arguments. In exchange, it means that when changing those arguments, build scripts no longer must be rebuilt from source. ### Fmt Step: Options `paths` and `exclude_paths` are now LazyPath lists. There is a convenience method to create them: `b.pathList`. ```diff - const fmt_include_paths = &.{ "lib", "src", "test", "tools", "build.zig", "build.zig.zon" }; - const fmt_exclude_paths = &.{ "test/cases", "test/behavior/zon" }; + const fmt_include_paths = b.pathList(&.{ "lib", "src", "test", "tools", "build.zig", "build.zig.zon" }); + const fmt_exclude_paths = b.pathList(&.{ "test/cases", "test/behavior/zon" }); ``` ### std.Build API * `b.build_root` (Directory) -> `b.root` (Path) * `ConfigHeader.Options`: `include_guard_override` -> `include_guard` * `LazyPath`: `getDisplayName` -> `format` ("{f}") * `LazyPath.basename`: removed since the value is not known until make phase * `b.findProgram` divided into `findProgram` and `findProgramLazy` and API future-proofed. * `ConfigHeader` now properly reports unused values for all styles ### std.Target API * parseCpuModel now returns optional rather than error ### Build System Behavior * When targeting Windows or Wine, artifact args added to Run steps used to modify PATH based on the set of directories containing the recursive set of DLL dependencies. Now this is only done for argv[0]. The motivation for also doing this for the other command line arguments is unclear, since those DLLs don't need to be loaded in order to execute argv[0]. ### Perf Data Point: `zig build -h` (cached) ``` Benchmark 1 (34 runs): master/zig build -h measurement mean ± σ min … max outliers delta wall_time 150ms ± 5.52ms 145ms … 165ms 4 (12%) 0% peak_rss 84.8MB ± 275KB 84.2MB … 85.1MB 0 ( 0%) 0% cpu_cycles 593M ± 4.01M 588M … 608M 2 ( 6%) 0% instructions 995M ± 52.5K 995M … 995M 0 ( 0%) 0% cache_references 25.8M ± 165K 25.4M … 26.1M 0 ( 0%) 0% cache_misses 651K ± 20.1K 619K … 697K 0 ( 0%) 0% branch_misses 918K ± 7.44K 906K … 935K 0 ( 0%) 0% Benchmark 2 (348 runs): branch/zig build -h measurement mean ± σ min … max outliers delta wall_time 14.3ms ± 744us 13.2ms … 23.3ms 8 ( 2%) ⚡- 90.4% ± 0.4% peak_rss 78.5MB ± 562KB 77.1MB … 81.4MB 7 ( 2%) ⚡- 7.4% ± 0.2% cpu_cycles 24.1M ± 821K 22.8M … 27.1M 3 ( 1%) ⚡- 95.9% ± 0.1% instructions 43.7M ± 23.8K 43.7M … 43.8M 56 (16%) ⚡- 95.6% ± 0.0% cache_references 1.46M ± 14.6K 1.40M … 1.50M 19 ( 5%) ⚡- 94.3% ± 0.1% cache_misses 142K ± 4.87K 127K … 157K 2 ( 1%) ⚡- 78.1% ± 0.4% branch_misses 126K ± 1.37K 120K … 129K 12 ( 3%) ⚡- 86.3% ± 0.1% ``` ### Perf Data Point: Running a subset of the toolchain test suite Fresh cache except in both cases I let the build runner / maker / configurer get cached beforehand. master: ``` $ time -v stage3/bin/zig build test-cases test-standalone -Dskip-release --seed 0 Elapsed (wall clock) time (h:mm:ss or m:ss): 2:09.93 Maximum resident set size (kbytes): 496512 ``` branch: ``` $ time -v stage3/bin/zig build test-cases test-standalone -Dskip-release --seed 0 --maker-opt=ReleaseFast Elapsed (wall clock) time (h:mm:ss or m:ss): 1:46.88 Maximum resident set size (kbytes): 495700 ``` It's only one data point, but the new thing is faster and less memory. As is expected from being compiled in optimized mode. That's the point of the changeset. ### Introduce the Concept of Configure Cache Poisoning If the cache is poisoned means that the **configure logic** had side effects, or otherwise did something that could not be tracked by the cache system. This is not to be confused with whether individual steps may have side effects when being evaluated; it has to do with the logic inside build.zig itself. For example, a `Run` step that prints "hello world" has side effects *at make time* and therefore does not warrant setting this flag, while checking for the existence of `scdoc` *at configure time* in order to choose the default value for a configuration option does. Keeping the cache pure will make `zig build` faster, bypassing the configurer process when identical configuration would be generated. When the cache is poisoned, the maker process will delete the build configuration file upon ingesting it since it cannot be reused. Currently the only way to poison the cache is to call `findProgram`. Advanced users can override the cache poisoning behavior with a CLI option: ``` --cache-poison[=mode] Override configuration caching behavior pure (default) Avoid false positive cache hits poisoned Don't cache the configuration disallowed Panics when cache would be poisoned ignored A little poison never hurt anybody ``` #### findProgram Immediately (in the configure phase), searches for an executable on the host that has more than one possible name. Names are searched in order, observing search prefixes first and then PATH environment variable. Calling this function poisons the configuration cache, so it is only appropriate when the existence of the program or its output needs to be observed by configuration logic. That's why there is a lazy variant of this function now. #### findProgramLazy Creates an anonymous `Step` that searches for an executable on the host that has more than one possible name. Returns the `LazyPath` of the found executable. The search only takes place if the `LazyPath` will be used by a depending `Step`. This API is useful in the following cases: * The binary is not named the same across all systems (for example "python" vs "python3"). * The binary may be produced by building from source rather than being globally installed and will therefore be possibly found in one of the search prefix paths. ### Removed Ability to Override Build Runner There is no concept of a "build runner" any more; it has been split in two: configurer and maker. Users of this feature will likely want to no longer override any logic, and instead consume the configuration file produced by configurer. If overriding one or the other of these is desired, the feature will need to be re-introduced (as --override-maker or --override-configurer). ## Followup Issues * [CLI flag to print path to the configuration file](https://codeberg.org/ziglang/zig/issues/35498) * test a bunch of third party projects / help people migrate * [search prefixes added at configuration time should be package-local](https://codeberg.org/ziglang/zig/issues/35472) * [introduce the concept of adding path dependencies of the configure script itself](https://codeberg.org/ziglang/zig/issues/35473) - don't forget to implement Cache.addPathPost and Configuration.Path.toCachePath - [make --watch rerun itself](https://github.com/ziglang/zig/issues/20602) * [Maker.WebServer: fix bad logic in serveTarFile](https://codeberg.org/ziglang/zig/issues/35457) * [Maker.WebServer: don't do linear search in the steps array](https://codeberg.org/ziglang/zig/issues/35458) * [maker: refactor and reuse the fuzz number parsing here (--maxrss, --debounce)](https://codeberg.org/ziglang/zig/issues/35459) * [handle missing cache hits when chaining two run steps](https://codeberg.org/ziglang/zig/pulls/30762) * [Absolute and cwd-relative paths in build cache](https://codeberg.org/ziglang/zig/issues/32097) * [build system fmt step with check=false does not acquire a write lock on source files](https://codeberg.org/ziglang/zig/issues/35204) * [enhance CheckFile step output when there is not a match](https://codeberg.org/ziglang/zig/issues/35208) * [stop leaking into global process arena. audit all uses of graph.arena](https://github.com/ziglang/zig/issues/20603) * reduce the size of Maker.Step.Extended (make Run smaller) probably by using an arena per make * consider using ReleaseFast by default for Maker * make the generated dependencies.zig be dependencies.zon and don't put absolute paths in there - and adjust dependencyInner to not openDir() * make more stuff use IndexType * make addExtra return Index using reflection * refactor with DefaultingEnum * get the target from the parent process instead * link_eh_frame_hdr should be DefaultingBool * make --foo, --no-foo CLI args uniform (make them -f args instead) * install steps should provide generated files for installed things, then delete the run step hack - but artifact install steps also add paths for dyn libs on windows * no more "artifact arg" to run step. if you want to run the post-install binary, get the lazy path from the install step. * UpdateSourceFiles: introduce Group * WriteFiles: introduce Group * re-examine the use case of adding file paths to Options steps * extract the reusable Configure abstractions and reuse it for Zir etc * add the ability to delete files to UpdateSourceFiles * merge the code of Maker.Step.Compile.checkCompileErrors with std.testing.expectEqualStrings * std.Build.Run: make addPathDir use LazyPath. This will require enhancing the env_map to support some values being strings and some values being LazyPaths. - also this is not the appropriate place to integrate with wine. move it to Maker logic * constrain the set of environment variables passed to configurer. they can ask for more but they will integrate properly with the cache system. * should ConfigHeader run in configurer and store the rendered string? * ConfigHeader: - TODO: use C-specific escaping instead of zig string literals - TODO: use nasm-specific escaping instead of zig string literals * enhance doctest to use "--listen=-" rather than operating in a temporary directory * Maker: eliminate memory allocation in the hot path (search for "TODO eliminate memory allocation here" x2) * print more stuff in --print-configuration - paths - unlazy deps - system integrations - available options * Maker.Step.InstallDir: update the call to truncatePath to first check dest stat. if already exists and length zero, skip the open() call and track the "all_cached" flag properly like the surrounding code. * Maker.Step.Run: when trying to interpret, learn the target from the binary directly rather than from relying on it being a Compile step. This will make this logic work even for the edge case that the binary was produced by a third party. * investigate why configurer takes so long to compile * fmt step: import zig fmt code directly rather than child proc? * add zig reduce functionality directly into the build system. detect when the compiler crashes and offer a command that will attempt to make a reproducer.

🎉 36 🚀 18

andrewrk added the

release notes

breaking

build system

labels 2026-05-23 10:01:18 +02:00

andrewrk added 1 commit 2026-05-23 10:01:19 +02:00

zig build: add CLI usage for --print-configuration 35a98f2ba7

bfredl commented 2026-05-23 13:14:34 +02:00

First-time contributor

Copy link

Is there a long-term reason that that Maker needs to be compiled at first use, and not simply being built in like zig maker or whatever? (I understand that it is much easier to hack on it during development this way!). As it lives in global cache and not per-project cache, it doesn't depend on any project specific options, no?

Is there a long-term reason that that Maker needs to be compiled at first use, and not simply being built in like `zig maker` or whatever? (I understand that it is much easier to hack on it during development this way!). As it lives in global cache and not per-project cache, it doesn't depend on any project specific options, no?

rohlem commented 2026-05-23 15:12:12 +02:00

First-time contributor

Copy link

@bfredl I think the reasoning here would be the same as for other subcommands like zig cc, zig libc, zig objcopy etc. being compiled on-demand instead of included in the zig binary. As far as I'm aware:

• ability to optimize further (based exactly on user's target: os/environment, cpu model)
• smaller binary / download size for zig itself
• support easier hacking

@bfredl I think the reasoning here would be the same as for other subcommands like `zig cc`, `zig libc`, `zig objcopy` etc. being compiled on-demand instead of included in the `zig` binary. As far as I'm aware: - ability to optimize further (based exactly on user's target: os/environment, cpu model) - smaller binary / download size for `zig` itself - support easier hacking

👍 1

andrewrk force-pushed build-runner-process from 35a98f2ba7 to 0d5f203baf 2026-05-23 21:19:26 +02:00 Compare

alexrp commented 2026-05-23 21:34:57 +02:00

Owner

Copy link

@andrewrk wrote in #35428 (comment):

• When targeting Windows or Wine, artifact args added to Run steps used to
  modify PATH based on the set of directories containing the recursive set of
  DLL dependencies. Now this is only done for argv[0]. The motivation for the
  former behavior is unclear.

Isn't this change going to cause transitive dependency DLLs to fail to load?

@andrewrk wrote in https://codeberg.org/ziglang/zig/pulls/35428#issue-5273132: > * When targeting Windows or Wine, artifact args added to Run steps used to > modify PATH based on the set of directories containing the recursive set of > DLL dependencies. Now this is only done for argv[0]. The motivation for the > former behavior is unclear. Isn't this change going to cause transitive dependency DLLs to fail to load?

andrewrk commented 2026-05-23 21:58:25 +02:00

Author

Owner

Copy link

Isn't this change going to cause transitive dependency DLLs to fail to load?

The difference is not in recursiveness, it is in whether the logic is done for only argv[0], or for argv[0] and also artifact args added to argv.

> Isn't this change going to cause transitive dependency DLLs to fail to load? The difference is not in recursiveness, it is in whether the logic is done for only argv[0], or for argv[0] and also artifact args added to argv.

👍 1

andrewrk added 4 commits 2026-05-23 23:20:43 +02:00

Maker.Step.Run: fix wrong allocator used a753d01e10

Maker: update macos file watching code to new api 91a1b5c663

Maker: fix compilation on windows 1a1e055e38

Maker: fix compilation on BSDs a9e58e2db1

andrewrk added 2 commits 2026-05-24 00:37:01 +02:00

zig build CLI: change --debug-maker to --maker-opt=[mode] ... cc9d13a813

the --debug- prefixed args are reserved for compiler debugging flags.

Maker: fix resolveLazyPath accidental mutation 5fd0284c5f

andrewrk added 2 commits 2026-05-24 01:50:19 +02:00

std.Build.Configuration: fix loading on big endian 09b4032f4f

Maker: fix regressed dyn lib symlink logic 5c6f92c004

andrewrk added 1 commit 2026-05-24 02:21:41 +02:00

Maker.Step.WriteFile: fix not creating dir entries 74bbcf9364

andrewrk added 4 commits 2026-05-24 06:49:08 +02:00

Maker.Step.Run: fix passing -L to qemu ae17540cac

std.Build.lazyImport: fix compilation errors b53090b021

ci: remove redundant comment ... 2018afff20

it says it right there in the echo text afterwards

fuzzer: get it working again a355bd316e

andrewrk force-pushed build-runner-process from a355bd316e to a27b0ba5c5 2026-05-24 22:59:13 +02:00 Compare

andrewrk force-pushed build-runner-process from a27b0ba5c5 to ecf7c2f621 2026-05-25 08:25:28 +02:00 Compare

andrewrk force-pushed build-runner-process from ecf7c2f621 to 8ce996a8c9 2026-05-25 22:26:24 +02:00 Compare

andrewrk force-pushed build-runner-process from 8ce996a8c9 to 4438a3faa4 2026-05-25 22:33:54 +02:00 Compare

andrewrk added 5 commits 2026-05-26 00:04:39 +02:00

zig build: remove --build-runner CLI parameter ... 970fd74979

There is no concept of a "build runner" any more; it has been split in two:
configurer and maker.

Users of this feature will likely want to no longer override any logic, and
instead consume the configuration file produced by configurer.

If overriding one or the other of these is desired, the feature will need to be
re-introduced (as --override-maker or --override-configurer).

Maker.Step: avoid unnecessary compilation failure ... 885b0b77ee

On s390x the cache line size is 256 so this check was failing. That's
not useful, just check only for more common cache line sizes.

Maker: implement relativePath with non-empty subpath for zig_exe 317ab034c9

LazyPath: store relative paths as actual strings 4544b4c902

Maker: restore commit: clear step inputs when resetting the step ... 3beaf781ca

I'm a bit confused because my understanding is that each step is
supposed to make its own decision about whether to clear its watch
inputs and start over, or retain them from the previous update. However,
without this fix in place, the problem from #35224 manifests itself
again.

Since this fix is in place in master branch, I'll leave it for now and
audit the file watching logic later.

andrewrk force-pushed build-runner-process from 3beaf781ca to 9571cba45b 2026-05-26 03:56:20 +02:00 Compare

andrewrk force-pushed build-runner-process from 9571cba45b to a9e0eb5340 2026-05-26 04:27:26 +02:00 Compare

andrewrk added 1 commit 2026-05-26 05:15:01 +02:00

Maker: add --debug-maker-leaks flag and fix some leaks f3dd10d40f

andrewrk added 3 commits 2026-05-26 05:45:19 +02:00

Maker.Step.Compile: fix memory leak in checkCompileErrors 5b022623cf

Maker.Step.Run: fix leak in evalGeneric 1d750d7067

Maker: print amount of arena memory used only when --debug-maker-leaks c9619d7086

1off referenced this pull request 2026-05-26 08:34:35 +02:00

WIP: Add Compilation Database Support to Zig Build System (compile_commands.json) #35462

FalsePattern referenced this pull request from FalsePattern/zigbrains 2026-05-26 11:00:17 +02:00

Broken with Zig 0.17.0 master branch #11

andrewrk merged commit 0ff175b69e into master 2026-05-26 18:00:45 +02:00

andrewrk referenced this pull request from a commit 2026-05-26 18:05:42 +02:00

Merge pull request 'zig build: separate the maker process from the configurer process' (#35428) from build-runner-process into master

andrewrk referenced this pull request 2026-05-26 18:06:11 +02:00

search prefixes added at configuration time should be package-local #35472

andrewrk referenced this pull request 2026-05-26 18:07:58 +02:00

introduce the concept of adding path dependencies of the build script itself #35473

bfredl referenced this pull request 2026-05-27 09:57:48 +02:00

fix(cache): handle missing cache hits when chaining two run steps #30762

andrewrk referenced this pull request 2026-05-27 20:59:39 +02:00

zig build CLI flag to print path to the configuration file #35498

squeek502 referenced this pull request 2026-05-30 00:45:42 +02:00

Add skip reason to build summary #30013

andrewrk referenced this pull request 2026-05-30 01:24:15 +02:00

build server protocol #35538

chrboesch referenced this pull request from ziglings/exercises 2026-05-31 12:45:45 +02:00

Unable to execute zig build #433

bcrist referenced this pull request from kudu/xmlread 2026-06-02 06:04:36 +02:00

Fix build.zig to work with both zig 0.16 and zig 0.17 #1

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

abi/f32

  

abi/ilp32

  

abi/sf

  

accepted

This proposal is planned.

  

arch/21k

  

arch/6502

  

arch/aarch64

  

arch/alpha

  

arch/amdgcn

  

arch/arc

  

arch/arc32

  

arch/arc64

  

arch/arm

  

arch/avr

  

arch/bfin

  

arch/bpf

  

arch/colossus

  

arch/cris

  

arch/csky

  

arch/dlx

  

arch/epiphany

  

arch/fr30

  

arch/frv

  

arch/hexagon

  

arch/hppa

  

arch/hppa64

  

arch/ia64

  

arch/kalimba

  

arch/kvx

  

arch/lanai

  

arch/lm32

  

arch/loongarch32

  

arch/loongarch64

  

arch/m32r

  

arch/m68k

  

arch/m88k

  

arch/mcore

  

arch/microblaze

  

arch/mips

  

arch/mips64

  

arch/mmix

  

arch/moxie

  

arch/mrisc32

  

arch/msp430

  

arch/nds32

  

arch/ns32k

  

arch/nvptx

  

arch/or1k

  

arch/powerpc

  

arch/powerpc64

  

arch/propeller

  

arch/riscv32

  

arch/riscv64

  

arch/rl78

  

arch/rx

  

arch/s390x

  

arch/sh

  

arch/sparc

  

arch/sparc64

  

arch/spirv

  

arch/spu

  

arch/tricore

  

arch/v850

  

arch/vax

  

arch/vc4

  

arch/ve

  

arch/wasm

  

arch/x86

  

arch/x86_64

  

arch/xcore

  

arch/xtensa

  

autodoc

The web application for interactive documentation and generation of its assets.

  

backend/c

The C backend outputs C source code.

  

backend/llvm

The LLVM backend outputs an LLVM bitcode module.

  

backend/self-hosted

The self-hosted backends produce machine code directly.

  

binutils

Zig's included binary utilities: zig ar, zig dlltool, zig lib, zig ranlib, zig objcopy, and zig rc.

  

breaking

Implementing this issue could cause existing code to no longer compile or have different behavior.

  

build system

The Zig build system - zig build, std.Build, the build runner, and package management.

  

debug info

An issue related to debug information (e.g. DWARF) produced by the Zig compiler.

  

docs

An issue with documentation, e.g. the language reference or standard library doc comments.

  

error message

This issue points out an error message that is unhelpful and should be improved.

  

frontend

Tokenization, parsing, AstGen, ZonGen, Sema, Legalize, and Liveness.

  

fuzzing

An issue related to Zig's integrated fuzz testing.

  

incremental

Reuse of internal compiler state for faster compilation.

  

lib/c

This issue relates to Zig's libc implementation and/or vendored libcs.

  

lib/compiler-rt

This issue relates to Zig's compiler-rt library.

  

lib/cxx

This issue relates to Zig's vendored libc++ and/or libc++abi.

  

lib/std

This issue relates to Zig's standard library.

  

lib/tsan

This issue relates to Zig's vendored libtsan.

  

lib/ubsan-rt

This issue relates to Zig's ubsan-rt library.

  

lib/unwind

This issue relates to Zig's vendored libunwind.

  

linking

Zig's integrated object file and incremental linker.

  

miscompilation

The compiler reports success but produces semantically incorrect code.

  

os/android

  

os/contiki

  

os/dragonfly

  

os/driverkit

  

os/emscripten

  

os/freebsd

  

os/fuchsia

  

os/haiku

  

os/hermit

  

os/hurd

  

os/illumos

  

os/ios

  

os/linux

  

os/maccatalyst

  

os/macos

  

os/managarm

  

os/netbsd

  

os/ohos

  

os/openbsd

  

os/plan9

  

os/redox

  

os/rtems

  

os/serenity

  

os/tvos

  

os/uefi

  

os/visionos

  

os/wasi

  

os/watchos

  

os/windows

  

proposal

This issue suggests language modifications. If it also has the "accepted" label then it is planned.

  

release notes

This issue or pull request should be mentioned in the release notes.

  

testing

This issue is related to testing the compiler, standard library, or other parts of Zig.

  

zig cc

Zig as a drop-in C-family compiler.

  

zig fmt

The Zig source code formatter.

  

zig reduce

The Zig source code reduction tool.

  

bounty

https://ziglang.org/news/announcing-donor-bounties

  

bug

Observed behavior contradicts documented or intended behavior.

  

contributor-friendly

This issue is limited in scope and/or knowledge of project internals.

  

downstream

An issue with a third-party project that uses this project.

  

enhancement

Solving this issue will likely involve adding new logic or components to the codebase.

  

infra

An issue related to project infrastructure, e.g. continuous integration.

  

optimization

A task to improve performance and/or resource usage.

  

question

No questions on the issue tracker; use a community space instead.

  

regression

Something that used to work in a previous version stopped working

  

upstream

An issue with a third-party project that this project uses.

No labels

abi/f32

abi/ilp32

abi/sf

accepted

arch/21k

arch/6502

arch/aarch64

arch/alpha

arch/amdgcn

arch/arc

arch/arc32

arch/arc64

arch/arm

arch/avr

arch/bfin

arch/bpf

arch/colossus

arch/cris

arch/csky

arch/dlx

arch/epiphany

arch/fr30

arch/frv

arch/hexagon

arch/hppa

arch/hppa64

arch/ia64

arch/kalimba

arch/kvx

arch/lanai

arch/lm32

arch/loongarch32

arch/loongarch64

arch/m32r

arch/m68k

arch/m88k

arch/mcore

arch/microblaze

arch/mips

arch/mips64

arch/mmix

arch/moxie

arch/mrisc32

arch/msp430

arch/nds32

arch/ns32k

arch/nvptx

arch/or1k

arch/powerpc

arch/powerpc64

arch/propeller

arch/riscv32

arch/riscv64

arch/rl78

arch/rx

arch/s390x

arch/sh

arch/sparc

arch/sparc64

arch/spirv

arch/spu

arch/tricore

arch/v850

arch/vax

arch/vc4

arch/ve

arch/wasm

arch/x86

arch/x86_64

arch/xcore

arch/xtensa

autodoc

backend/c

backend/llvm

backend/self-hosted

binutils

breaking

build system

debug info

docs

error message

frontend

fuzzing

incremental

lib/c

lib/compiler-rt

lib/cxx

lib/std

lib/tsan

lib/ubsan-rt

lib/unwind

linking

miscompilation

os/android

os/contiki

os/dragonfly

os/driverkit

os/emscripten

os/freebsd

os/fuchsia

os/haiku

os/hermit

os/hurd

os/illumos

os/ios

os/linux

os/maccatalyst

os/macos

os/managarm

os/netbsd

os/ohos

os/openbsd

os/plan9

os/redox

os/rtems

os/serenity

os/tvos

os/uefi

os/visionos

os/wasi

os/watchos

os/windows

proposal

release notes

testing

zig cc

zig fmt

zig reduce

bounty

bug

contributor-friendly

downstream

enhancement

infra

optimization

question

regression

upstream

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

4 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

ziglang/zig!35428

No description provided.