authorgravatar for mlugg@mlugg.co.ukMatthew Lugg <mlugg@mlugg.co.uk> 2025-08-02 02:01:31+01:00
committergravatar for mlugg@mlugg.co.ukMatthew Lugg <mlugg@mlugg.co.uk> 2025-08-02 08:56:19+01:00
loge98aeeb73fba942c8e061bb8158ed073a7b19e1d
tree11a653d1b4763d5ef09098d173cb7965d3d39974
parent239efa7e670498a5745ee7db96948c875422c815

std.Build: keep compiler alive under `-fincremental --webui`

Previously, this only applied when using `-fincremental --watch`, but `--webui` makes the build runner stay alive just like `--watch` does, so the same logic applies here. Without this, attempting to perform incremental updates with `--webui` performs full rebuilds. (I did test that before merging the PR, but at that time I was passing `--watch` too -- which has since been disallowed -- so I missed that it doesn't work as expected without that option!)

1 files changed, 1 insertions(+), 1 deletions(-)

lib/std/Build/Step/Compile.zig+1-1
...@@ -1851,7 +1851,7 @@ fn make(step: *Step, options: Step.MakeOptions) !void {...@@ -1851,7 +1851,7 @@ fn make(step: *Step, options: Step.MakeOptions) !void {
1851 const maybe_output_dir = step.evalZigProcess(1851 const maybe_output_dir = step.evalZigProcess(
1852 zig_args,1852 zig_args,
1853 options.progress_node,1853 options.progress_node,
1854 (b.graph.incremental == true) and options.watch,1854 (b.graph.incremental == true) and (options.watch or options.web_server != null),
1855 options.web_server,1855 options.web_server,
1856 options.gpa,1856 options.gpa,
1857 ) catch |err| switch (err) {1857 ) catch |err| switch (err) {