mlugg fe855691f6
std.Build.Step.Run: inherit build runner cwd
Right now, if you override the build root with `--build-root`, then
`Run` steps can fail to execute because of incorrect path handling in
the compiler: `std.process.Child` gets a cwd-relative path, but also has
its cwd set to the build root. The latter behavior is really weird; it
doesn't match my expectations, nor does it match how we spawn child
`zig` processes. So, this commit makes the child process inherit the
build runner's cwd, as `LazyPath.getPath2` *expects* it to.

After investigating, this behavior dates all the way back to 2017; it
was introduced in 4543413. So, there isn't any clear/documented reason
for this; it should be safe to revert, since under the modern `LazyPath`
system it is strictly a bug AFAICT.
2025-05-21 01:45:05 +01:00
..
2024-12-19 17:10:03 -05:00
2025-05-17 18:00:17 -04:00
2024-07-23 11:43:12 -07:00
2025-04-03 14:55:04 -07:00
2025-02-05 13:58:15 +01:00
2024-08-22 08:44:08 +02:00
2025-02-06 14:23:23 -08:00
2025-03-17 21:56:17 +03:30
2025-02-22 14:32:48 -08:00
2024-08-07 00:48:32 -07:00
2024-07-31 16:57:42 -07:00
2025-05-17 18:00:17 -04:00
2024-08-29 23:43:52 +01:00
2025-05-03 20:09:51 +01:00
2025-02-06 14:23:23 -08:00
2025-02-03 09:14:37 +00:00