Generally speaking, you don't control the Bazel output configuration-specific directory, unless you use transitions (and even there, the name is unpredictable) :-/
The name you are seeing here (x64_windows_fastbuild in this example) is currently
a Bazel implementation detail, computed from command-line options like --cpu, --platforms or --compilation_mode and probably a few others which can change between Bazel releases. Also, when transitions exist in your configured graph, each new build configuration instance will gets is new output configuration directory, but with very unpredictable names like
k8-fastbuild-ST-edfdb45b22e6.
There is an
open Github issue to change this logic to more predictable scheme in the future, but don't hold your breadth :-)
Hope this helps,
- Digit