-
Notifications
You must be signed in to change notification settings - Fork 10.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[lldb-vscode] Instructions for vscode seems outdated #63655
Comments
@llvm/issue-subscribers-lldb |
According to microsoft/vscode#178667, using the command This created the |
I hit this just yesterday. @walter-erquinigo do you know what the canonical way should be? Michael's reference seems authoritative. When I followed the existing instructions it just didn't show up in the installed extensions, and did wonder if I needed an entry in that main json file too. |
@DavidSpickett , Michaels' reference is right. Tbh I haven't installed lldb-vscode manually in at least two years, so I'm not surprised that things have changed. I'll send a PR updating the README. |
lldb-vscode had installation instructions based on creating a folder inside ~/.vscode/extensions, which no longer works. A different installation mechanism is needed based on a VSCode command. More can be read in the contents of this patch. Closes llvm#63655
lldb-vscode had installation instructions based on creating a folder inside ~/.vscode/extensions, which no longer works. A different installation mechanism is needed based on a VSCode command. More can be read in the contents of this patch. Closes #63655
lldb-vscode had installation instructions based on creating a folder inside ~/.vscode/extensions, which no longer works. A different installation mechanism is needed based on a VSCode command. More can be read in the contents of this patch. Closes llvm#63655 (cherry picked from commit 098c927)
The steps in the Readme wont lead to a working extension, there seems to be substantial difference in current vscode versions. Seems to be required to add an entry to
extensions.json
aswell.I only manages to install the tool by building my own
vsix
with a simple shell script calling the system installedlldb-vscode
tool.The text was updated successfully, but these errors were encountered: