This revision was automatically updated to reflect the committed changes. Closed by commit rG5a52c5c42669: Summary: This documentation patch adds information to allow remote users to… (authored by HenriqueBucher).
Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D135577/new/ https://reviews.llvm.org/D135577 Files: lldb/tools/lldb-vscode/README.md Index: lldb/tools/lldb-vscode/README.md =================================================================== --- lldb/tools/lldb-vscode/README.md +++ lldb/tools/lldb-vscode/README.md @@ -36,6 +36,12 @@ $ cp /path/to/a/built/liblldb.so . ``` +It is important to note that the directory `~/.vscode/extensions` works for users logged in locally to the machine. If you are remoting into the box using Visual Studio Code's Remote plugins (SSH, WSL, Docker) it will look for extensions on `~/.vscode-server/extensions` only and you will not see your just installed lldb-vscode plug-in. If you want this plugin to be visible to remoting users, you will need to either repeat the process above for the `~/.vscode-server` folder or create a symbolic link from it to `~/.vscode/extensions`: + +``` +$ cd ~/.vscode-server/extensions +$ ln -s ~/.vscode/extensions/llvm-org.lldb-vscode-0.1.0 llvm-org.lldb-vscode-0.1.0 +``` If you want to make a stand alone plug-in that you can send to others on macOS systems: @@ -61,6 +67,8 @@ This is handy if you want to debug and develope the `lldb-vscode` executable when adding features or fixing bugs. + + # Configurations Launching to attaching require you to create a [launch configuration](https://code.visualstudio.com/Docs/editor/debugging#_launch-configurations). This file
Index: lldb/tools/lldb-vscode/README.md =================================================================== --- lldb/tools/lldb-vscode/README.md +++ lldb/tools/lldb-vscode/README.md @@ -36,6 +36,12 @@ $ cp /path/to/a/built/liblldb.so . ``` +It is important to note that the directory `~/.vscode/extensions` works for users logged in locally to the machine. If you are remoting into the box using Visual Studio Code's Remote plugins (SSH, WSL, Docker) it will look for extensions on `~/.vscode-server/extensions` only and you will not see your just installed lldb-vscode plug-in. If you want this plugin to be visible to remoting users, you will need to either repeat the process above for the `~/.vscode-server` folder or create a symbolic link from it to `~/.vscode/extensions`: + +``` +$ cd ~/.vscode-server/extensions +$ ln -s ~/.vscode/extensions/llvm-org.lldb-vscode-0.1.0 llvm-org.lldb-vscode-0.1.0 +``` If you want to make a stand alone plug-in that you can send to others on macOS systems: @@ -61,6 +67,8 @@ This is handy if you want to debug and develope the `lldb-vscode` executable when adding features or fixing bugs. + + # Configurations Launching to attaching require you to create a [launch configuration](https://code.visualstudio.com/Docs/editor/debugging#_launch-configurations). This file
_______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
