Using iocshDev support in an application

This support module allows iocsh command to be run as a result of record processing.

Several files need minor modifications to use iocshDev instrument support in an application.

1. Add the full path to the iocshDev support directory to the application configure/RELEASE file:
   iocshDev=xxxx/modules/instrument/iocshDev/<release>
   Where <release> is the release number of of the iocshDev support.
2. Add iocshDev support to application database definition file
   The application database definition file must include the database definition files for the iocshDev support. There are two ways that this can be done:
   • If you are building your application database definition file from an xxxInclude.dbd file you include the additional database definitions in that file:
     include "base.dbd"
     include "iocshDev.dbd"
     
   • If you are building your application database definition file from the application Makefile you specify the aditional database definitions there:
     xxx_DBD += base.dbd
     xxx_DBD += iocshDev.dbd
     
3. Add the iocshDev support libraries to the application
   You must link the iocshDev support library and the ASYN support library with the application. Add the following lines:
   xxx_LIBS += iocshDev
   xxx_LIBS += asyn
   before the
   xxx_LIBS += $(EPICS_BASE_IOC_LIBS)
   in the application Makefile.
4. Load the iocshDev support database records in the application startup script:
   dbLoadRecords("db/iocshDev.db,"P=<P>,R=<R>,L=<L>,A=<A>")
   You'll have to provide appropriate values for the PV name prefixes (<P> and <R>).

Installation and Building

1. Create an installation directory for the module. The path name of this directory should end with modules/instrument/iocshdevsup.
2. Place the distribution file into this directory.
3. Execute the following commands:
   cd modules/instrument/iocshDev
   gunzip iocshDev<release>.tar.gz
   tar xvf iocshDev<release>.tar
   cd <release>
   Where <release> is the release number of of the iocshDev support.
4. Edit the configure/RELEASE file and set the paths to your installation of EPICS base and ASYN.
5. Execute make in the top level directory.