Unable to open source file outside workspaceFolder from project outline

hi @bobbrow, I am using 1.4.2 CMake Tools on macOS, but the issue is still there:

Unable to open 'main.cpp': Unable to read file '/Users/admin/Projects/A/console/Users/admin/Projects/A/src/main.cpp' (Error: Unable to resolve non-existing file '/Users/admin/Projects/A/console/Users/admin/Projects/A/src/main.cpp').

The project structure looks like:

A $ tree -L 2 .
.
├── README.md
├── console
│   ├── build
│   └── CMakeLists.txt
├── src
│   └── main.cpp
└── third-party

with this simple setup:

set(MAIN_SOURCE_DIR "../src")

file(GLOB_RECURSE CPP_HEADERS ${MAIN_SOURCE_DIR}/*.hpp)
file(GLOB_RECURSE CPP_SOURCES ${MAIN_SOURCE_DIR}/*.cpp)

add_executable(
    A
    ${CPP_HEADERS}
    ${CPP_SOURCES}
)

As you can see, the error reports a path with <CMakeLists Dir>+<Absolute Source Path>, which is duplicate and totally wrong.

'/Users/admin/Projects/A/console/Users/admin/Projects/A/src/main.cpp'

Platform and Versions Operating System:macOS CMake Version:3.18.4 VSCode Version:1.50.1 CMake Tools Extension Version: 1.4.2 Compiler/Toolchain: Clang 11

_Originally posted by @mutoo in https://github.com/microsoft/vscode-cmake-tools/issues/1254#issuecomment-713215418_

[andreeis]

@sleiner, your contribution is in 👍. If all goes according to plans, we should release CMake Tools 1.7.2 tomorrow. Until then, here’s a vsix with your change, if needed: https://github.com/microsoft/vscode-cmake-tools/actions/runs/814930130.

[k0pernicus]

Hi everyone, I have the exact same issue than @bobbrow (EDIT: sorry, it was @mutoo).

If I don’t make any mistake, we are following a tutorial to create a sort of graphic engine on multiple platforms, using C++ and SDL: https://marcelbraghetto.github.io/a-simple-triangle/2019/03/02/part-02/

In this part, the author shows how to configure it’s own VSCode instance using Cmake and Cmake Tools (vector-of-bool version, not from microsoft), but following the steps VSCode + extensions does not follow the rules and create another full path inside the current workspace folder.

I expect that the configuration of the extensions change, or something we missed, because using the scripts on the console directly works, check the code directly and build the binary.

Setup:

• macOS Catalina 10.15.7
• VSCode 1.50.1
• CMake (twxs) version 0.0.17
• CMake Tools (Microsoft) version 1.5.0