Skip to content

Commit

Permalink
Merge pull request #53 from rock-core/syskit_tips
Browse files Browse the repository at this point in the history
add a section about some tips for Syskit
  • Loading branch information
g-arjones committed Mar 9, 2018
2 parents 26581bc + 4a7a820 commit 9e2251f
Showing 1 changed file with 44 additions and 0 deletions.
44 changes: 44 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -168,6 +168,50 @@ entries, that is:
- `${rock:which:cmd}` expands to the full path to the command `cmd` within
the autoproj workspace's PATH.

### Syskit Workflow

The only syskit-specific workflow available right now is the ability to
configure the Syskit IDE to open file links directly in VSCode. To do so, open
`$HOME/.config/syskit.conf` and create or update the `[Main]` section to have

~~~
cmdline=code --goto %FILEPATH:%LINENO
~~~

For instance, a freshly created `syskit.conf` would look like:

~~~
[Main]
cmdline=code --goto %FILEPATH:%LINENO
~~~

Moreover, as part of a good general Syskit workflow in VSCode, we recommend
creating task entries to start `rock-gazebo` and the IDE. For instance:

~~~
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
{
"label": "rock-gazebo right_margin",
"type": "shell",
"command": "cd ${workspaceRoot} ; ../../.autoproj/bin/autoproj exec rock-gazebo right_margin",
"isBackground": true,
"problemMatcher": []
},
{
"label": "syskit (gazebo)",
"type": "shell",
"command": "cd ${workspaceRoot} ; ../../.autoproj/bin/autoproj exec syskit ide -rgazebo",
"isBackground": true,
"problemMatcher": []
}
]
}
~~~

## Known Issues

See [the issue page on GitHub](https://github.com/doudou/rock_website/issues?q=is%3Aopen+is%3Aissue+label%3Avscode)

0 comments on commit 9e2251f

Please sign in to comment.