Multiple project roots not configured when one root is a subdirectory of the other

[harrymander]

Multiple project roots not configured when one root is a subdirectory of the other

[harrymander]

Have updated with a simpler reproducible example

[Evelyn-001]

@harrymander, thanks for providing the demo project. Today we try to repro this this issue with below steps: Could you please help check the below picture if it describes your issue? If not, could you please provide a video about repro steps to us? If we miss or misunderstand anything, please let us know. Thanks.
System info: Ubuntu 22.04.4 LTS

VS code version: 1.88.1

CMake Extension version: v 1.17.17& v 1.88.30 pre-release

Repro steps:
1.Open the project folder with VSCode.
2. Run "delete cache and reconfigure" command to configure project.
3. Observe the output
System info: Ubuntu 22.04.4 LTS

VS code version: 1.88.1

CMake Extension version: v 1.17.17& v 1.88.29 pre-release

Repro steps:
1.Open the project folder with VSCode.
2. Run "delete cache and reconfigure" command to configure project.
3. Observe the output

Actual Results: configure a new CMake root under ${workspaceFolder}/build

[harrymander]

@Evelyn-001 Yes that is the observed behaviour. Build files are always written to a build directory in the top-level project directory, even if configuring inside the nested directory (when I would expected a directory to be created at nested/build).

Not sure what you mean by "install Node using the method the customer mentioned".

[Evelyn-001]

@harrymander, Sorry, please ignore this sentence. Now that we have reproduced your issue, we will continue to investigate the issue. We will get back to you if there are any updates. Thanks for your support.