...
(a) Create the following directories:
$IOC/ioc-b34-my01
$IOC_DATA/ioc-b34-my01
$APP/MyApp Test (look at this as an example)
Now create the EPICS application using standard templates and scripts:
(b) cd $APP/Test
mkdir Development
cd Development
You are currently in:
/afs/slac/g/lcls/epics/R3-14-12-3_1-0/iocTop/Test/Development
This is referred as the EPICS application top directory: <TOP>
makeBaseApp.pl -t slac MyAppMyTest
Now, an EPICS application has been created for you with the application name 'MyAppMyTestApp'.
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) Add the following line:
LINUX_KERNEL_MODULES=$(PACKAGE_SITE_TOP)/linuxKernel_Modules
(iii) 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
...
