[Lldb-commits] [lldb] [lldb-dap] Create a typescript extension for lldb-dap (PR #75515)

Greg Clayton via lldb-commits lldb-commits at lists.llvm.org
Thu Dec 14 12:22:41 PST 2023


================
@@ -27,58 +31,43 @@ get a full featured debugger with a well defined protocol.
 
 # Installation for Visual Studio Code
 
-Installing the plug-in involves creating a directory in any location outside of
-`~/.vscode/extensions`. For example, `~/vscode-lldb` is a valid one. You'll also
-need a subfolder `bin`, e.g. `~/vscode-lldb/bin`. Then copy the `package.json`
-file that is in the same directory as this documentation into it, and symlink
-the `lldb-dap` binary into the `bin` directory inside the plug-in directory.
+Installing the plug-in is very straightforward and involves just a few steps:
 
-Finally, on VS Code, execute the command
-`Developer: Install Extension from Location` and pick the folder you just
-created, which would be `~/vscode-lldb` following the example above.
-
-If you want to make a stand alone plug-in that you can send to others on UNIX
-systems:
+- Install a modern version of node (e.g. `v20.0.0`).
+- On VS Code, execute the command `Install 'code' command in PATH`. You need to
+  do it only once. This enables the command `code` in the PATH.
+- In the `lldb-dap` folder, package and install the extension:
----------------
clayborg wrote:

Maybe we can checking a python script that just does this instead of talking about all the things we need to do? To make this easier, we could make sure a directory could contain all of the stuff in the right structure so we would just copy a folder like ` lldb/tools/lldb-dap/extension` over into the `~/.vscode/extensions/<name>` with a rename. This might be a good place for all of the typescript to be checked in instead of the `src-ts` directory?

https://github.com/llvm/llvm-project/pull/75515


More information about the lldb-commits mailing list