christoph/wamr
1
Fork 0
Code Releases Activity

Update CIs and documents to make naming of generated binaries consistent (#1823)

Browse Source
This commit is contained in:
TianlongLiang
2022-12-24 09:17:39 +08:00
committed by GitHub
parent d04f3988c3
commit 6fd8001eb6
6 changed files with 97 additions and 58 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
test-tools/wamr-ide/VSCode-Extension/README.md
View File

@ -3,13 +3,16 @@
### An integrated development environment for WASM.
# How to debug this extension
> Note that when you download and
> decompress to get .vsix file from [our release](https://github.com/bytecodealliance/wasm-micro-runtime/releases).
> It's by default that the `source debugging` feature is not enabled.
> If you want to enable `source debugging` feature of this extension,
> you could either download `lldb` from [our release](https://github.com/bytecodealliance/wasm-micro-runtime/releases) and put them in correct path
mentioned in this [instruction](./resource/debug/README.md) (This is recommended way),
> or you could build `lldb` yourself follow this [instruction](./resource/debug/README.md)
> Note that when you download and
> decompress to get .vsix file from [our release](https://github.com/bytecodealliance/wasm-micro-runtime/releases).
> It's by default that the `source debugging` feature is not enabled.
> If you want to enable the `source debugging` feature of this extension,
> you could download `lldb` from [our release](https://github.com/bytecodealliance/wasm-micro-runtime/releases)
> (This is the recommended way, and you could do it with a single click in VS Code).
> Then if you want to use your customized lldb patch,
> you could build your own version of `lldb`
> and then follow this [instruction](./resource/debug/README.md)
> to put them in the correct path
### 1. open `VSCode_Extension` directory with the `vscode`