mlugg 36499c251c std.Build.Step.Run: prefix relative path arguments with './'
This is necessary in two cases:

* On POSIX, the exe path (`argv[0]`) must contain a path separator
* Some programs might treat a file named e.g. `-foo` as a flag, which
  can be avoided by passing `./-foo`

Rather than detecting these two cases, just always include the prefix;
there's no harm in it.

Also, if the cwd is specified, include it in the manifest. If the user
has set the cwd of a Run step, it is clearly because this affects the
behavior of the executable somehow, so that cwd path should be a part of
the step's manifest.

Resolves: #24216
2025-06-18 22:45:05 +01:00
..
2024-12-19 17:10:03 -05:00
2025-06-05 13:45:52 +01:00
2025-06-15 22:15:06 +01:00
2025-06-13 21:23:41 -04:00
2025-06-15 14:15:18 -04:00
2025-06-16 13:22:19 +03:30
2025-02-05 13:58:15 +01:00
2025-06-16 13:22:19 +03:30
2024-08-22 08:44:08 +02:00
2025-02-06 14:23:23 -08:00
2025-02-22 14:32:48 -08:00
2024-08-07 00:48:32 -07:00
2025-05-24 10:52:56 +02:00
2024-07-31 16:57:42 -07:00
2025-06-15 14:15:18 -04:00
2025-06-16 13:22:19 +03:30
2024-08-29 23:43:52 +01:00
2025-06-12 13:55:41 +01:00
2025-06-16 13:22:19 +03:30
2025-06-16 13:22:19 +03:30
2025-02-06 14:23:23 -08:00
2025-02-03 09:14:37 +00:00