-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #91 from epics-containers/md
Final changes for the new copier template based workflow
- Loading branch information
Showing
7 changed files
with
160 additions
and
271 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,14 +7,20 @@ TODO: this needs completing - pull all configuration discussions into | |
one place. Most of these will come from the original Setting up the | ||
Workspace document. | ||
|
||
| | | | ||
|---|---| | ||
|
||
## Git Configuration | ||
|
||
This setting replaces https URLS for github repositories with ssh URLs. This is useful for the ibek-support submodule in the ioc-XXX repositories because it uses an HTTPS URL so that it can be built anywhere. When you want to push changes it is more convenient to use ssh URLs. | ||
``` | ||
[url "ssh://[email protected]/"] | ||
insteadOf = https://github.com/ | ||
``` | ||
|
||
| | | | ||
|---|---| | ||
|
||
## Vscode Settings | ||
|
||
These settings can be edited using `Ctrl-Shift-P`: `Preferences: Open User Settings: (JSON)` | ||
|
@@ -46,3 +52,5 @@ For a much richer command line experience, it is recommended to use the zsh shel | |
"terminal.integrated.defaultProfile.linux": "zsh", | ||
``` | ||
|
||
| | | | ||
|---|---| |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,32 +1,23 @@ | ||
# Working with Support Modules | ||
|
||
:::{Warning} | ||
This tutorial is out of date and will be updated soon. | ||
This tutorial is an early draft and is not yet complete. | ||
::: | ||
|
||
TODO: this is currently a stub with some pointers. | ||
|
||
TODO: suggest that we will make a new Stream Device that will be a | ||
simple echo server. Use this to step through the process of creating a | ||
new support module. | ||
|
||
This is a type 3. change from the list at {any}`ioc-change-types`. | ||
|
||
If you are starting a new support module then the preceding tutorials | ||
have covered all of the skills you will need. | ||
|
||
To work on a new support module you will need a Generic IOC project to | ||
work inside. You could choose to create two new projects: | ||
|
||
```{eval-rst} | ||
:ioc-MyNewDeviceSupport: | ||
In the tutorial on {doc}`generic_ioc`, we created a new Generic IOC container image that wrapped the existing support module `lakeshore340`. | ||
|
||
a Generic IOC container definition based on ioc-template | ||
If you wanted to create a completely new support module then you would use a very similar workflow to the above. | ||
|
||
Once you have created the project(s), working on the support module will | ||
look very similar to the procedures set out here `debug_generic_ioc` | ||
``` | ||
In brief, the steps are: | ||
|
||
Once you have created the project(s), working on the support module will | ||
look very similar to the procedures set out here {any}`debug_generic_ioc` | ||
- Create a new Generic IOC project using the <https://github.com/epics-containers/ioc-template> | ||
- Create a new folder in /workspaces/YOUR_SUPPORT_MODULE_NAME | ||
- Link the new folder to the epics support folders: | ||
- ln -s /workspaces/YOUR_SUPPORT_MODULE_NAME /epics/support/YOUR_SUPPORT_MODULE_NAME | ||
- TODO the ibek command `ibek dev support YOUR_SUPPORT_MODULE_NAME` will do this in future | ||
- Now work on your support module and get it compiling | ||
- Then add `ibek-support` for the new module as per {doc}`generic_ioc` | ||
- create an example instance in the Generic IOC project to test your work | ||
- When ready, push your new support and new ioc-support projects. |
This file was deleted.
Oops, something went wrong.