You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Alternatively you can use LaunchRequest instead of AttachRequest for automatic debug server launch.
141
+
In case of IoT.js Debug it looks like this:
142
+
```json
143
+
{
144
+
"name": "IoT.js: Launch",
145
+
"type": "iotjs",
146
+
"request": "launch",
147
+
"program": "iotjs",
148
+
"address": "localhost",
149
+
"port": 5001,
150
+
"localRoot": "${workspaceRoot}",
151
+
"stopOnEntry": false,
152
+
"debugLog": 0,
153
+
"args": [
154
+
"--start-debug-server",
155
+
"--debugger-wait-source"
156
+
]
157
+
}
158
+
```
159
+
160
+
These configuration options are required. Manifest:
161
+
-`name`: The name which will be visible in the debug view
162
+
-`type`: This must be `iotjs` otherwise the debug session wont start
163
+
-`request`: Type of the session start
164
+
-`program`: Runtime executable for debug server. Default is iotjs. If you debug on desktop use
165
+
absolute path to executable (e.g.:/path/to/iotjs/build/x86_64-linux/debug/bin/iotjs)
166
+
-`address`: IP address on which the server listening. Default is `localhost`
167
+
-`port`: Debug port to attach to. Default is `5001`
168
+
-`localRoot`: The local source root directoy, most cases this is the `${workspaceRoot}`
169
+
-`stopOnEntry`: Autmoatically stop the program after launch, the IoT.js will stop on the first breakpoint for now, no matter that is enabled or not.
170
+
-`debugLog`: The type of the debug log, you can choose from 0 to 4:
171
+
- 0: none
172
+
- 1: Error (show errors only)
173
+
- 2: Debug Session related (requests and their responses)
174
+
- 3: Debug Protocol related (communication between the engine and the client)
175
+
- 4: Verbose (each log type included)
176
+
-`args`: Arguments for debug server. In case of IoT.js use --start-debug-server and --debugger-wait-source.
177
+
136
178
137
179
After the engine is running you can start the debug session inside the extension host by pressing the `F5` key or click on the green triangle in the debug panel.
138
180
If the client (VSCode extension) is connected then you have to see that file which is running inside the engine or if you started the engine in waiting mode you will get a prompt window where you can select that file what you want to running and then you can see where the execution is stopped. Now you can use the VSCode debug action bar to control the debug session.
@@ -151,6 +193,19 @@ If you want to use the development extension just like any other extension in yo
151
193
# After this just reload the VSCode and the extension will be "installed"
152
194
$ cp .~/.vscode/extensions/ -r
153
195
```
196
+
# Tizen Studio
197
+
Now you can use the extension to debug Tizen applications.
198
+
Requirements:
199
+
- The latest version of [Tizen Studio with CLI](https://developer.tizen.org/development/tizen-studio/download)
200
+
201
+
After installing Tizen Studio you can add the following lines of information to launch.json:
This enables the extension to install required packages for Tizen Studio to be able to create IoTjsApp native project. The installation may take several minutes.
154
209
155
210
# License
156
211
IoT.js VSCode extension is Open Source software under the [Apache 2.0 license](LICENSE). Complete license and copyright information can be found within the code.
0 commit comments