Automatically detect case sensitivity in folders (on Windows) about vscode-cpptools HOT 6 OPEN

And if I running fsutil.exe file setCaseSensitiveInfo C:\test\ disable, the problem disappears.

We do have a setting that might help with this. Can you try enabling the case sensitive file support in the C++ extension? "C_Cpp.caseSensitiveFileSupport": "enabled".

from vscode-cpptools.

It looks like the issue may not be with the # sign but with the file being within your D: drive. If this is a partition, then our extension may not be able to open the file correctly. As you can see, we are correctly escaping the pounds sign using "%23" to be recognized as a correct filepath.

See below example where the "#" is included in my path:

This has however revealed a bug within our Add #include feature where we do not pick up header files under a directory with the # symbol.

Could you please replicate this scenario in your C: drive?

from vscode-cpptools.

@browntarik I fixed the missing backslash in the issue report. The original text was: d:\#\cwd, but the Markdown renderer displayed it as d:#\cwd. Can you try again? Also try with an explicit includePath instead of recursive includes.

@Zewbiee you can help us out by running the C/C++: Log Diagnostics command and sharing the output with us.

from vscode-cpptools.

It looks like the issue may not be with the # sign but with the file being within your D: drive. If this is a partition, then our extension may not be able to open the file correctly. As you can see, we are correctly escaping the pounds sign using "%23" to be recognized as a correct filepath.

Could you please replicate this scenario in your C: drive?

@browntarik You are right. I cannot reproduce this problem under c:\#\cwd .

Maybe the following steps are the real way to reproduce it:

1. Create an empty folder C:\test
2. Execute

fsutil.exe file setCaseSensitiveInfo C:\test\ enable

3. Open C:\test in vscode
4. Create hello.cpp and hello.h in C:\test
5. Include hello.h in hello.cpp
6. There will be a problem saying: cannot open source file "hello.h"

@bobbrow Running C/C++: Log Diagnostics in this scenario gives:

-------- Diagnostics - 1/17/2024, 1:23:45 PM
Version: 1.18.5
Current Configuration:
{
    "name": "Win32",
    "includePath": [
        "c:/test/**"
    ],
    "defines": [
        "_DEBUG",
        "UNICODE",
        "_UNICODE"
    ],
    "intelliSenseMode": "windows-gcc-x64",
    "cStandard": "c17",
    "cppStandard": "c++17",
    "intelliSenseModeIsExplicit": false,
    "cStandardIsExplicit": true,
    "cppStandardIsExplicit": true,
    "mergeConfigurations": false,
    "compilerPath": "D:\\Programs\\mingw64\\bin\\g++.exe",
    "compilerPathIsExplicit": true,
    "browse": {
        "path": [],
        "limitSymbolsToIncludedHeaders": true
    }
}
cpptools version (native): 1.18.3.0
Translation Unit Mappings:
[ C:\test\hello.cpp ]:
    C:\test\hello.cpp
    C:\test\hello.h *
Translation Unit Configurations:
[ C:\test\hello.cpp ]:
    Process ID: 34700
    Memory Usage: 50 MB
    Compiler Path: D:\Programs\mingw64\bin\g++.exe
    Includes:
        D:\Programs\mingw64\lib\gcc\x86_64-w64-mingw32\13.2.0\include\c++
        D:\Programs\mingw64\lib\gcc\x86_64-w64-mingw32\13.2.0\include\c++\x86_64-w64-mingw32
        D:\Programs\mingw64\lib\gcc\x86_64-w64-mingw32\13.2.0\include\c++\backward
        D:\Programs\mingw64\lib\gcc\x86_64-w64-mingw32\13.2.0\include
        D:\Programs\mingw64\lib\gcc\x86_64-w64-mingw32\13.2.0\include-fixed
        D:\Programs\mingw64\x86_64-w64-mingw32\include
        C:\test
    Defines:
        _DEBUG
        UNICODE
        _UNICODE
    Standard Version: c++17
    IntelliSense Mode: windows-gcc-x64
    Other Flags:
        --g++
        --gnu_version=130200
Total Memory Usage: 50 MB

------- Workspace parsing diagnostics -------
Number of files discovered (not excluded): 2577

And if I running fsutil.exe file setCaseSensitiveInfo C:\test\ disable, the problem disappears.

from vscode-cpptools.

"C_Cpp.caseSensitiveFileSupport": "enabled".

It works.

But the error prompt is really confused. Will it be improved in future versions?

from vscode-cpptools.

Currently, the language server only sees this problem as a "file not found" issue. To fix this we'd have to scan your folders for the case sensitive flag. And if we do that, we might be able to automatically turn on the case sensitive file support. It's a good next step for the feature, but I don't have an ETA at this time as to when we will be able to work on it.

from vscode-cpptools.