Support case sensitive path resolution on Windows 10

[oakad]

Newer Windows 10 builds control case sensitive resolution of the file paths on a per directory basis. This is needed to ensure proper interoperability with Unix tooling (one substantial user of this feature is the new Windows Subsystem for Linux).

If case sensitive file path resolution is enabled for the workspace enclosing directory and some elements of the directory path are mixed case, Bazel will fail outright with the fatal error "The system cannot find the file specified" (because of file path case squashing performed).

It will be nice if there was a setting to enable a fully case sensitive file path resolution on Windows without any case squashing or like (I understand, this was an original behavior of Bazel before #2613).

Reference: https://blogs.msdn.microsoft.com/commandline/2018/02/28/per-directory-case-sensitivity-and-wsl/

[aiuto]

Note that this is also a requirement for Mac. Plenty of developers use case sensitive mac volumes.

[sgowroji]

Hi there! We're doing a clean up of old issues and will be closing this one. Please reopen if you’d like to discuss anything further. We’ll respond as soon as we have the bandwidth/resources to do so.

[oakad]

It is very unfortunate that Bazel is still essentially broken on Windows (many issues) because of a relatively minor thing in a single Java class.