This RELEASE of EPICS for use by LCLS is based on EPICS R3.14.9 from the APS.

CVS Tag:  base-R3-14-9-lcls1

Pre-Req: 
(a) Only support RHEL4 32 bit
(b) This installation will consume about 2 Gbytes of disk space (we think!)
(c) Your Linux System Admin should install any prerequisite packages
(d) Only bash has been tested for a supported unix shell. 

Download the tar files in: 
http://www.slac.stanford.edu/grp/lcls/controls/downloads/epics/

Step 1: Download the EPICS packages:
           base-R3-14-9-lcls1.tgz
           extensions-rev1-R3-14-9.tgz
           modules-R3-14-9-lcls1.tgz

        Download the RTEMS package:
           rtems-4.7.1-p2.tgz

        Download the PERL builder scripts:
           baseBuilder.pl
           extBuilder.pl
           moduleBuilder.pl

        Download the setup file: 
           epicsSetup.bash

Step 2: Next unpack the packages where you want.
        Just remember that you will need to modify epicsSetup.bash 
        to point to where the packages reside and the corresponding version 
        as well.

        Typical directories for a site epics top directory called myTop would 
        be:
        (a) myBaseTop/epics/base
        (b) myExtTop/epics/extensions
        (c) myModTop/epics/modules
        (d) myRtemsTop/rtems
    
        for lcls eBeam production Control System: 
        myBaseTop = myExtTop = myModTop = myRtemsTop = /usr/local/lcls
        This is recommended for simplicity, although the Tops do not have to 
        be equal. Please create all the Tops listed above. 

        To unpack the packages:

        > cd myBaseTop/epics/base
        > tar zxvf base-R3-14-9-lcls1.tgz
        > cd myExtTop/epics/extensions
        > tar zxvf extensions-rev1-R3-14-9.tgz
        > cd myModTop/epics
        > tar zxvf modules-R3-14-9-lcls1.tgz
        > cd myRtemsTop/rtems
        > tar zxvf rtems-4.7.1-p2.tgz
        > ln -s rtems-4.7.1-p2 rtems-4.7.1
 
Step 3: For local installation, you must edit epicsSetup.bash to change 
        any local parameters: directory names and package versions.

        The following parameters must be set according to the Tops from Step 2
        as well as the appropriate version tags (you can find this information
        from the directory structure after unpack):
        (a) EPICS_HOST_ARCH
        (b) EPICS_SITE_TOP
        (c) EPICS_BASE_VER
        (d) RTEMS_SITE_TOP
        (e) RTEMS_VER
        (f) EXTENSIONS_SITE_TOP
        (g) EXTENSIONS_VER
        (h) EPICS_MODULES_TOP

Step 4: Set up your environment for the build by sourcing the setup file
        (make sure you are in bash shell):

        > . epicsSetup.bash

Step 5: Now it's time to build the epics components.
        The 3 perl build scripts customize relevant config files for your 
        environment and run make:

           1.  ./baseBuilder.pl
           2.  ./extBuilder.pl
           3.  ./moduleBuilder.pl

        They can be run from anywhere, but should be run in this order to 
        satisfy dependencies. The setup file you modified and sourced in 
        previous steps should set up all necessary environment variables for 
        the scripts to run successfully.
        To see command line parameters and required environment variables for 
        each script, simply enter e.g.,
 
        > baseBuilder.pl help 

        Short summary of script arguments and example:
        baseBuilder.pl
           optional argument: clean, clean uninstall, or all
           example: baseBuilder.pl all

        extBuilder.pl
           Sytem prerequisites to build edm:
           libungif, libungif-devel, libpng, and libpng-devel

           optional argument: clean, clean uninstall, or all
           example: extBuilder.pl clean
        
        moduleBuilder.pl
           This perl script will be all of the common EPICS 
           driver/device/record support. Some modules will have system 
           prerequisites:
           -- streamdevice: needs "pcre" and "pcre-devel"
           -- snmp: needs net-snmp, net-snmp-libs, net-snmp-devel,
                    net-snmp-utils, and net-snmp-perl
           Note please be sure that your system admin installs the pre-req
           packages to build "streamdevice" and "snmp" modules.
           Modules_Build_Order.txt (this is a text file located in
           $EPICS_MODULES_TOP, listing modules and 
           their versions, in the proper build order).

           optional argument: clean, clean uninstall, or all
           example: moduleBuilder.pl $EPICS_MODULES_TOP/Modules_Build_Order.txt clean uninstall 

        Examples to build the packages:

        > baseBuilder.pl all
        > extBuilder.pl all
        > moduleBuilder.pl $EPICS_MODULES_TOP/Modules_Build_Order.txt all

        To log the output from build to a file, redirect script output, e.g.
        > baseBuilder.pl all > baseBuilder.log 2>&1

Step 6: During each build script execution, enjoy a cup a coffee. If things 
        don't work, send email to ernesto@slac.stanford.edu

Step 7: Whenever you begin to use EPICS you will need to setup your 
        environment for run-time behavior. Please make sure the setup file 
        is sourced; if not, do the following (in bash shell):

        > . epicsSetup.bash

Step 8: To run EDM

        > edm &