Correct paths on case-sensitive filesystems #18
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On Windows 10 with WSL enabled, you can enable NTFS case sensitivity through
fsutil.exe file SetCaseSensitiveInfo [folder] enable
. This causes Git (both Windows and WSL) and compilers to malfunction, and is very difficult to fix. But Git on Windows (case-insensitive by default) encounters breakage as well, just less often.This PR fixes the consistency of upper/lowercase folders, files, and references to them in C++
#include
, Visual Studio .vcxproj[.filters], and CMake files. I verified that compilation works in CMake, but didn't fully verify in Visual Studio, where IntelliSense is broken with case sensitivity enabled (wrecking the user experience).This PR should have no effects; it does not enable NTFS case sensitivity, you have to do it yourself.
Based on a diff by @Gumball2415.