cmake.getLaunchTargetFilename returns nothing (again?)

[emece67]

Brief Issue Summary

Same as #1692 and apparently related to #1412 and #461 , but this time (re-)appeared in version 1.18.43. Up to 1.18.42 it worked OK.

Thanks & regards.

CMake Tools Diagnostics

No response

Debug Log

No response

Additional Information

No response

[gcampbell-msft]

emece67 Have you selected your launch target? I notice that when running the "echo" task from here: #1692 (comment) and modifying it to also use ${command:cmake.getLaunchTargetFilename}, it says it can't find any and asks me to pick a launch target. However, once I've selected a launch target in the Project status view:

It works as expected:

[emece67]

Hope this helps:

[gcampbell-msft]

emece67 I'm not able to repro this on multiple different large test projects. Also, I've tested the most recent pre-release channel and found that this issue doesn't reproduce. Could you share a repro project?

[emece67]

Hi again:

Not in a repo, but I've prepared a minimal example.

Note that I'm working on Windows 11 with MSYS2 using clang. But python, cmake and ninja are not the MSYS2 ones, but "straight" Windows executables. Also, I'm debugging with lldb, so using CodeLLDB.

hello.zip

[gcampbell-msft]

v-cathyzhang (@Yingzi1234) Could you assist in helping us reproduce this?

[gcampbell-msft]

emece67 Are you able to successfully configure?

[emece67]

Yes, it both configures and builds.

[gcampbell-msft]

emece67 Thanks for posting this issue. I've been able to track this down. There was an issue created here: #3541, that was fixed in this way: #3764.

Could you try to workaround this by using a different build directory? Also, what machine are you working on? My thoughts right now are that the PR that was merged may be a fix for only Linux scenarios.

[emece67]

I think you're right. Changing paths from ${sourceDir}/~build/${presetName} to ${sourceDir}/.build/${presetName} or ${sourceDir}/build/${presetName}fixed it.

I'm working in Windows 11, where paths such as ${sourceDir}/~build/${presetName} are perfectly valid (in my systems, paths starting with ~ are not synced, thus my insistance on using ~).

[gcampbell-msft]

emece67 I would agree, I think we'll insert a quick fix where we only do that adjustment in linux and/or mac. Thanks for the issue