...
(a) Create the following directories:
$IOC/ioc-b34-my01
$IOC_DATA/ioc-b34-my01
$APP/MyApp (look at this as an example)
Now create the EPICS application using standard templates and scripts:
(b) cd $APP
makeBaseApp.pl -t slac MyApp
Now, an EPICS application has been created for you with the application name 'MyApp'.
Look through the RELEASE_SITE file in the top level that was automatically created for you.
Notice how EPICS base path, modules path, App path, EPICS version and other EPICS environment variables were set for you to point to
the new EPICS base R3-14-12-3_1-0.
Now, look at the configure/RELEASE file.
This file needs modifications from what was automatically generated:
I have commented in the example application $APP/MyApp/configure/RELEASE what needs to change.
(i) Add the following line to the beginning of RELEASE file:
include $(TOP)/RELEASE_SITE
(ii) Replace the TEMPLATE_TOP variable as follows:
TEMPLATE_TOP=$(EPICS_BASE)/templates/makeBaseApp/top
(iii) Add the following line:
LINUX_KERNEL_MODULES=$(PACKAGE_SITE_TOP)/linuxKernel_Modules/
(iviii) Change the various module version numbers as needed for your application.
Ensure that the specific versions included in your RELEASE file DO EXIST under the modules directory
and that they have been built for the linuxRT-x86 target.
Use Event module event-R4-1-3 or greater.
AUTOSAVE_MODULE_VERSION=autosave-R5-0_1-0
IOCADMIN_MODULE_VERSION=iocAdmin-R3-1-12_1-1
EVENT_MODULE_VERSION=event-R4-1-3
(v) Now 'make' your application from the top level directory $APP/MyApp to ensure your changes to RELEASE files are good:
...
