bazel: Windows: don't shell out to `cmd.exe`
Description of the problem / feature request / question:
cmd.exe doesn’t support UNC paths so we can’t shell out to tools through it and use long paths.
Example where this occurs: WindowsFileSystem.createDirectoryJunction
Related issue: https://github.com/bazelbuild/bazel/issues/2181
Environment info
- Operating System: Windows 10
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 1
- Comments: 16 (16 by maintainers)
Commits related to this issue
- Windows: launcher no longer depends on cmd.exe See https://github.com/bazelbuild/bazel/issues/2190 Change-Id: If665af264a23be0219c75ae087dd25db74d5e386 — committed to laszlocsomor/bazel by laszlocsomor 6 years ago
- Windows: java launcher no longer calls cmd.exe See https://github.com/bazelbuild/bazel/issues/2190 Change-Id: If665af264a23be0219c75ae087dd25db74d5e386 — committed to laszlocsomor/bazel by laszlocsomor 6 years ago
- Windows: java launcher no longer calls cmd.exe See https://github.com/bazelbuild/bazel/issues/2190 Closes #5005. Change-Id: If665af264a23be0219c75ae087dd25db74d5e386 PiperOrigin-RevId: 192575414 — committed to bazelbuild/bazel by laszlocsomor 6 years ago
- CommandBuilder: remove useShell and setWorkingDir Remove the .useShell method, expect callers to just pass the shell interpreter if they need it. This removes the argument vector transformation heuri... — committed to laszlocsomor/bazel by laszlocsomor 6 years ago
Generally don’t use cmd, because MS announced that they will (finally!!) be deprecating it (over some time): http://www.osnews.com/story/29502/Microsoft_replaces_cmd_with_PowerShell_in_new_Windows_10_build