Failed to set up project in a subfolder of a git repository

[ncoghlan]

Failed to set up project in a subfolder of a git repository

[ncoghlan]

Checking the folder's VSCode settings, I think the key change from before/after the reinstall is that after the reinstall CMake-Tools automatially set the CMake source directory in the folder settings:

    "cmake.sourceDirectory": "/path/to/repo/cpp_embedding_demo"

I'm not sure if there was a command I could have run beforehand to sort that out.

I think that discovery may mean this issue is a duplicate of #1042 (a general UX report around the handling of a missing top-level CMakeLists.txt file, which I had found before filing this issue, but also before I discovered that an uninstall+reinstall of the extension fixed the problem, so I thought it wasn't directly related)

[ncoghlan]

Even though it's building, this is still behaving strangely. All the artifacts are still ending up in a top level build folder, instead of inside the embedding demo folder.

[ncoghlan]

Setting cmake.buildDirectory and then restarting VSCode was also necessary to resolve the problem with artifacts still being emitted to the top-level directory.

[v-frankwang]

@ncoghlan I used a simple project to reproduce your problem but was not able to reproduce it, would you be able to provide a simple project that can reproduce this problem so that we can reproduce it, it would be great if you could also provide some screenshots, it would be a great help for us to deal with this problem later. I look forward to hearing from you!

Here are my steps to reproduce it:
ENV:
CMake tools：v1.18.43
C/C++: v1.20.5
vscode: v1.19.1(user setup)

[ncoghlan]

It won't be this week, but I'll try the simple example next week. If it work for me too, then I think it will make the most sense to write this off as not reproducible.

[v-frankwang]

@ncoghlan Thank you very much for your reply, it's very much appreciated that you can provide a reproduction project in the next week, and we'll get to work on the issue as soon as we receive the project from you!

[gcampbell-msft]

@ncoghlan To recap all of this, it does sound like there may be improvements to be had, and they are tracked here: #1042.

As for the other issues, you were able to workaround them by setting the cmake.buildDirectory and cmake.sourceDirectory?

I'm looking forward to your repro because if Quick start has issues we'd definitely want to investigate. Thanks!