Closed DocLock17 closed 9 months ago
In the first pictures you changed the systems setting and not the local workspace settings. As said in the README only changing the local (workspace) settings.json is the right way. (Btw this is true for every vscode extension, that the local settings override the global settings)
I included a picture of me manually setting the local workspace settings.json and it still isn't working though?
Is this not the workspace settings.json? :
One question, are you using VScodium and not VSCode?
To be clear, is your extension not meant to be compatible with VS-Codium?
Perhaps I am just confused as to your target?
It's only partially compatible, since all of the Microsoft stuff is not available there. And tbh I won't spent much time for vscodium
Completely understood. It was originally my hope to submit a simple solution and make your life easier. Now that I know it is not that simple, I will simply continue to use my workaround.
I did prepare these two YouTube videos on setup with workarounds for Codium+Linux users.
https://www.youtube.com/watch?v=RkbZG6g83dE
https://www.youtube.com/watch?v=Q8WZJ1qu6mg
You are certainly welcome to use these links or not as you see fit. I would love for them to be of use to you, but I expect nothing in particular. I really appreciate your extension, and I am grateful for your help and contribution! Thank you!
Hope this helps
Using VSCodium on Linux Mint Debugger Appears to be Path Setting Broken
Understanding clang must be set as selected compiler
Found C_Cpp_Runner.debuggerPath Here:
Set it to LLDB as directed:
Get this error when attempting to run:
I checked the settings.json file but didn't see any update to the file. So I manually updated too:
Repeating my test I get the same error
Looking at launch.json I see:
By changing line 6 to 'lldb' this regains functionality:
However, this file is generated and gets overwritten so I seem to have to set this in the extension template itself. I made a YouTube video to show people how to do this until a better solution becomes available. NOTE: the error and apparent solution appear the same using 'gcc' as well.