update generic_ioc to 3.4.0

Author: gilesknap

docs/how-to/builder2ibek.md

@@ -6,7 +6,7 @@ builder beamline to epics-containers. i.e. those whose beamlines
 have a BLxxY-BUILDER project.
 :::
 
-TODO: this page is WIP and will be updated by Feb 2024.
+TODO: this page is WIP and will be updated by May 2024.
 
 `builder2ibek` is a tool to convert DLS builder XML to ibek instance YAML.
 It is for working with converting IOC instances to epics-containers.

docs/how-to/builder2ibek.support.md

@@ -6,7 +6,7 @@ a DLS support module with builder support into an epics-containers
 Generic IOC. i.e. support modules that have an `etc/builder.py` file.
 :::
 
-TODO: this page is WIP and will be updated by Feb 2024.
+TODO: this page is WIP and will be updated by May 2024.
 
 `builder2ibek.support` is a tool to convert DLS builder support modules
 into ibek support YAML for the `ibek-support` repository.

docs/tutorials/generic_ioc.md

@@ -71,13 +71,16 @@ your personal GitHub user space.
     <b>ioc-adsimdetector</b>
     <b>   </b><font color="#FFAF00"><b>ioc-lakeshore340</b></font>
     <font color="#5F87AF">🎤</font><b> A One line description of the module</b>
-    <b>   </b><font color="#FFAF00"><b>Generic IOC for the lakeshore 340 temperature controller</b></font>
+    <b>   </b><font color="#FFAF00"><b>ttttt</b></font>
     <font color="#5F87AF">🎤</font><b> Git platform hosting the repository.</b>
     <b>   </b><font color="#FFAF00"><b>github.com</b></font>
     <font color="#5F87AF">🎤</font><b> The GitHub organisation that will contain this repo.</b>
-    <b>   </b><font color="#FFAF00"><b>YOUR_GITHUB_ACCOUNT</b></font>
+    <b>   </b><font color="#FFAF00"><b>gilesknap</b></font>
     <font color="#5F87AF">🎤</font><b> Remote URI of the repository.</b>
-    <b>   </b><font color="#FFAF00"><b>[email protected]:YOUR_GITHUB_ACCOUNT/ioc-lakeshore340.git</b></font>
+    <b>   </b><font color="#FFAF00"><b>[email protected]:gilesknap/ioc-lakeshore340.git</b></font>
+    <font color="#5F87AF">🎤</font><b> Does this IOC require RTEMS support? At present RTEMS cross-compilation</b>
+    <b>is restricted to PowerPC beatnik boards (those used at DLS).</b>
+    <b>   </b><font color="#FFAF00"><b>No</b></font>
     </pre>
 
 1. Make the first commit and push the repository to GitHub.
@@ -95,7 +98,7 @@ your personal GitHub user space.
    ./build
    # DLS users make sure you have done: module load vscode
    code .
-   # reopen in container
+   # reopen in container (ctrl-shift-p reopen in container)
    ```
 
 As soon as you pushed the project, GitHub Actions CI will start building the project. This will make a container image of the template project, but not publish it because there is no release tag as yet. You can watch this by clicking on the `Actions` tab in your new repository.
@@ -310,7 +313,7 @@ FOLDER=$(dirname $(readlink -f $0))
 set -xe
 
 # doxygen is used in documentation build for the developer stage
-ibek support apt-install --only=dev doxygen
+ibek support apt-install doxygen
 
 # get the source and fix up the configure/RELEASE files
 ibek support git-clone ${NAME} ${VERSION} --org https://github.com/DiamondLightSource/
@@ -322,6 +325,9 @@ ibek support register ${NAME}
 #ibek support add-libs
 #ibek support add-dbds
 
+# global config settings
+${FOLDER}/../_global/install.sh
+
 # compile the support module
 ibek support compile ${NAME}
 # prepare *.bob, *.pvi, *.ibek.support.yaml for access outside the container.
@@ -409,7 +415,7 @@ and create a file called `lakeshore340.ibek.support.yaml`. Add the following
 contents:
 
 ```yaml
-# yaml-language-server: $schema=https://github.com/epics-containers/ibek/releases/download/1.6.2/ibek.support.schema.json
+# yaml-language-server: $schema=https://github.com/epics-containers/ibek/releases/download/2.0.1/ibek.support.schema.json
 
 module: lakeshore340
 
@@ -561,11 +567,11 @@ https://github.com/<YOUR GITHUB ACCOUNT>/ioc-lakeshore340/releases/download/<VER
 This would then be the URL you would put at the top of any IOC instances using
 your released Generic IOC.
 
-To create the instance we create a folder in `ioc-examples` and create a IOC Instance definition there as follows:
+To create the instance we create a folder in `bl00t-ea-test-01` and create a IOC Instance definition there as follows:
 
 ```bash
-mkdir -p /workspaces/ioc-lakeshore340/ioc-examples/bl16i-ea-ioc-07/config/
-cd /workspaces/ioc-lakeshore340/ioc-examples/bl16i-ea-ioc-07/config/
+mkdir -p /workspaces/ioc-lakeshore340/services/bl00t-ea-test-01/config/
+cd /workspaces/ioc-lakeshore340/services/bl00t-ea-test-01/config/
 code ioc.yaml
 ```
 
@@ -574,7 +580,7 @@ Add the following contents to the new yaml file:
 ```yaml
 # yaml-language-server: $schema=/tmp/ibek.ioc.schema.json
 
-ioc_name: "{{ ioc_yaml_file_name }}"
+ioc_name: "{{ __utils__.get_env('IOC_NAME') }}"
 
 description: auto-generated by https://github.com/epics-containers/builder2ibek
 
@@ -614,7 +620,7 @@ cd /epics/support/lakeshore340/etc/simulations/
 Now create a new terminal in VSCode (Terminal -> New Terminal) and run:
 
 ```bash
-ibek dev instance /workspaces/ioc-lakeshore340/ioc-examples/bl16i-ea-ioc-07
+ibek dev instance /workspaces/ioc-lakeshore340/services/bl00t-ea-test-01
 cd /epics/ioc
 make
 ./start.sh