Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Contact Murali or Ernest to have them built and installed. Murali has a python script that
automatically discovers the module dependencies and builds them in the correct order for all targets.

6. What Where and how do I create a new EPICS application?  How do I need to setup a new EPICS APP and IOC to use linuxRT-86 OS? (Ex. 'vioc-b34-my01' for 'MyApp')

When the go_epics*.bash script was sourced, several environment variables pertaining to EPICS were setup in your bash shell:

The following is true for any version of EPICS - but in this context, version R3-14-12-3_1-0.

Some variables are paths to ''TOP-level' directories:

...

$IOC_DATA is the data directory. This is where the outputs from the ioc all iocs and in some case inputs are stored.

...

Fill out an online form provided by SCCS to obtain permissions for your ioc to write to this directory.
:

https://www-rt.slac.stanford.edu/rt3/SelfService/Forms/IocNfs.html
 

(a) Create the following directories:
$IOC/ioc-b34-my01
$IOC_DATA/ioc-b34-my01
$APP/Test (look at this as an example)


Now create the your EPICS application MyTest as below using standard templates and scripts:

(b) cd $APP/Test

This is where you will be creating/checking out from CVS, several versions of your MyTest application, as you continue to develop.

Now create a sandbox area for MyTest.

mkdir  mkdir Development

(c) 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>top directory for your EPICS application: TOP

Now create your EPICS application MyTest using a perl script that automates this creation process as well as standardizes several file and directory structures:
makeBaseApp.pl -t slac MyTest

If you would like to know what this perl script can do type:



Now, an EPICS application has been created for you with the application name 'MyTestApp'.

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.

...