@@ -214,8 +213,8 @@ where:
cd
mkdir myapp
cd myapp
-/usr/local/epics/baseR3.13.0.beta11/bin/solaris/makeBaseApp.pl -t example example
-/usr/local/epics/baseR3.13.0.beta11/bin/solaris/makeBaseApp.pl -i -t example example
+/usr/local/epics/baseR3.13.0.beta12/bin/solaris/makeBaseApp.pl -t example example
+/usr/local/epics/baseR3.13.0.beta12/bin/solaris/makeBaseApp.pl -i -t example example
Inspect Files
@@ -262,9 +261,9 @@ convenient to have the console port of the IOC attached to a scrolling
window on your workstation.
Test
-See the description of the example given in section makeBaseApp below.
-Also try some of the vxWorks shell commands described in chapter "IOC Test
-facilities" of the Application Developer's Guide.
+See the description of the example given in section Templates
+Supplied with base . Also try some of the vxWorks shell commands described
+in chapter "IOC Test facilities" of the Application Developer's Guide.
Introduction
@@ -399,7 +398,11 @@ The application directory structure appears as follows:
...
iocBoot/
iocxxx/
- ...
+ ...
+ bin/
+ <host_arch>
+ <target_arch>
+ ...
Each <top> area is a separately managed set of applications.
Separately managed means that each <top> can be using it's
own release of software obtained from outside the application, e.g. a release
@@ -410,10 +413,11 @@ a single iocBoot directory appear. The xxxApp areas are created by application
developers as needed. The iocBoot directory contains a subdirectory for
each ioc that belongs to that <top> area. No IOC belongs to
more than one <top> area. All software components needed by
-IOCs are built in the xxxApp directories. Each IOC is booted from it's
-subdirectory under iocBoot. The only important source file in a boot directory
-is the st.cmd file which is executed after vxWorks is started on an ioc.
-The st.cmd file merely loads various files built in the xxxApp directories.
+IOCs are built in the xxxApp directories. Each IOC is booted from bin/<target_arch>
+and uses a startup file from it's subdirectory under iocBoot. The
+only important source file in a boot directory is the st.cmd file
+which is executed after vxWorks is started on an ioc. The st.cmd file
+loads various files built in the xxxApp directories.
Application developers decide what constitutes a <top>.
For example, at APS, the Linac is completely contained in a single <top>
@@ -452,11 +456,12 @@ Releases of share are created. A release contains built and installed
object modules. Other <top> areas take things from releases
of share rather then from share itself.
-
The releases of share, which are dependent on releases of epics
-base, are named:
+
At aps the releases of share, which are dependent on releases
+of epics base, are named:
baseXXXshareYYY
where XXX is the epics base release and YYY is a release of share
-for that base release. The share releases are stored at locations:
+for that base release. At aps the share releases are stored at
+locations:
/usr/local/iocapps/iocsys/baseXXXshareYYY
If it is necessary to obtain a bug fix or enhancement to a single module
from EPICS base or a share release, the application developer
@@ -467,8 +472,6 @@ so that you remember to use the version from share after share
is rebuilt.
Note: Other software packages can be handled like share.
-For example at APS/ASD our applications use releases of sharerf,
-epicsHideos, and hideos.
Tools
The following tools are used:
@@ -529,10 +532,9 @@ Structure
RULES_ARCHS
RULES_DIRS
RULES_TOP
- makeIoccdcmds.pl
- makeNfsCommands.pl
+ makeIocCdCommands.pl
xxxApp/
- src/ or xxxSrc
+ src/ or xxxSrc or xxxsrc
Makefile
* Makefile.Host
* Makefile.Vx
@@ -542,7 +544,7 @@ Structure
* <example and/or user supplied code>
* <example and/or user supplied state programs>
* <user menu, recordtype, device, driver database defs>
- Db/ or xxxDb
+ Db/ or xxxDb or xxxdb
Makefile
* <record instance files>
* <record template and substitution files>
@@ -553,6 +555,7 @@ Structure
iocxxx/
* Makefile
* st.cmd
+** cdCommands
** dbd/
<installed database description files>
** include/
@@ -670,7 +673,7 @@ of Makefiles below.
These files contain definitions included in the various makefiles.
-
-CONFIG
+CONFIG
-
This is the file in which you add to or modify make variables in epics
@@ -681,15 +684,16 @@ This specifies the vxWorks architecture to build. If your site builds base
for multiple target architectures but your iocs only use a single architecture,
overriding this variables saves build time.
-
-CONFIG_APP
+CONFIG_APP
-
This file contains definitions for external products such as epics base
and share. You should edit this file if you are using external products
-besides epics_base,and share.
+besides epics_base,and share. Follow the
+models already in the file.
-
-RELEASE
+RELEASE
-
This file specifies the location of external products such as epics base.
@@ -709,17 +713,24 @@ This variable must be defined.
-
This variable which is optional, specifies the location of a release of
a <top> area containing code that can be shared by other applications.
+
+-
+TEMPLATE_TOP
+
+-
+This variable specifies the location of the template top area for makeBaseApp.
IMPORTANT:Each of the above variables must be specified with a full
path name.
-RULES.Db
+RULES.Db
-This file contains rules for building database files from templates.
+This file contains rules for building database files from templates and
+rules for capfast files.
-RULES.Host
+RULES.Host
The template file includes the RULES.Host from base. If you want
@@ -727,7 +738,7 @@ to add rules that apply to all Makefile.Host files then this is
the place to add the rules.
-RULES.Vx
+RULES.Vx
The template file includes the RULES.Vx from base. If you want
@@ -735,44 +746,57 @@ to add rules that apply to all Makefile.Vx files then this is
the place to add the rules.
-RULES.ioc
+RULES.ioc
This is a file containing rules for the Makefiles in the directories from
-which iocs are booted. It makes the soft links needed to boot an ioc. It
-should not be necessary to modify this file.
+which iocs are booted.
-RULES.iocBoot
+RULES.iocBoot
This is a file containing rules for the Makefiles in the iocBoot directory.
It should not be necessary to modify this file.
-RULES_ARCHS
+RULES_ARCHS
This file includes the RULES_ARCHS from base. It is seldom necessary
to modify this file.
-RULES_DIRS
+RULES_DIRS
This file includes the RULES_DIRS from base. It is seldom necessary
to modify this file.
-RULES_TOP
+RULES_TOP
-All applications except SHARE just include SHARE/config/RULES_TOP.
+This file includes RULES_TOP from base. If MASTER_IOCAPPS is defined it
+also runs a utility that creates soft links to the master ioc. This feature
+only works if the host operating system supports soft links.
+
+
+makeIocCdCommands.pl
+
+
+This is a perl script that generates a cdCommands file for use
+by iocs.
base.dbd and <app>Include.dbd
-These files are used to configure database definitions for the following:
+NOTE: A version of bases.dbd can be obtained from
+
+<epics_base>/templates/makeBaseApp/top/exampleApp/src.
+
+
+These files are used to configure database definitions for the following:
-
menus
@@ -792,7 +816,7 @@ breakpoint tables
When gnumake is executed, an expanded file, i.e. a file with all
include statements expanded, is installed into:
<top>/dbd/
-with the name specified by DBDNAME in Makefile.Vx.
+with the name specified by DBDNAME in Makefile.Host.
base.dbd contains definitions obtained from the base release.
It contains definitions like:
@@ -819,12 +843,20 @@ from the desired support.
is the place where you define locally built support.
baseLIBOBJS
-This file defines all the object modules for record, device, and driver
-support supplied by EPICS. Since the file is intimately related to base.dbd,
-if base.dbd (is, is not) used in a particular xxxApp/src directory, then
-baseLIBOBJS should (be, not be) used in that directory.
-baseLIBOBJS contains definitions as follows:
+
+
+NOTE: A version of baseLIBOBJS can be obtained from
+
+<epics_base>/templates/makeBaseApp/top/exampleApp/src.
+
+
+This file defines all the object modules for record, device, and driver
+support supplied by EPICS. Since the file is intimately related to base.dbd,
+if base.dbd (is, is not) used in a particular xxxApp/src
+directory, then baseLIBOBJS should (be, not be) used in that directory.
+
+
baseLIBOBJS contains definitions as follows:
#LIBOBJS += $(EPICS_BASE_BIN)/aaiRecord.o
#LIBOBJS += $(EPICS_BASE_BIN)/aaoRecord.o
LIBOBJS += $(EPICS_BASE_BIN)/aiRecord.o
@@ -843,8 +875,8 @@ Thus it has a definition for all record, device, and drivers supplied in
EPICS base. Some record types and ALL hardware device and driver support
are proceeded by the comment symbol "#". You are expected to edit this
file and select the desired support routines, by removing the '#' from
-the front of the appropriate lines. Makefile.Vx contains rules that will
-combine all support into a single module called xxxSupport.
+the front of the appropriate lines. Makefile.Vx contains rules
+that will combine all support into a single module called xxxSupport.
APOLOGY: It would be nice if this file could be automatically
generated. This is not possible because there is no naming convention for
@@ -855,89 +887,271 @@ The vxWorks startup file is described in a later section.
makeBaseApp
-NOTE: two versions of makeBaseApp exist. makeBaseApp is a bourne
-script and makeBaseApp.pl is a perl script. They produce nearly identical
-results.
+makeBaseApp is a perl script that creates application areas. It can create
+the following:
+
+makeBaseApp creates directories and then copies template files with replacements
+into the newly created directories. Epics base supports two sets of template
+files: simple and example. These are meant for simple applications. Each
+site, however, can provide it's own set of template files which provide
+additional functionality. This section will describe the functionality
+of makeBaseApp itself and the next section will describe details about
+the simple and example templates.
+
+makeBaseApp has the following usage:
+
<base>/bin/<arch>/makeBaseApp.pl [options] app ...
+ create application directories
+<base>/bin/<arch>/makeBaseApp.pl -i [options] ioc ...
+ create ioc boot directories
+where
+ app Application name (the created directory will have "App" appended to name))
+ ioc IOC name (The created directory will have "ioc" prepended to name)
+
+ -t type Set the application type (-l for a list of valid types)
+ If not specified, type is taken from environment
+ If not found in environment, "default" is used
+ -T top Set the template top directory (where the application templates are)
+ If not specified, top path is taken from config/RELEASE
+ If config does not exist, top path is taken from environment
+ If not found in environment, the templates from EPICS base are used
+ -l List valid application types for this installation
+ If this is specified the other options are not used
+ -a arch Set the IOC architecture (e.g. mv167)
+ If not specified, you will be prompted
+ -b base Set the location of EPICS base (full path)
+ If not specified, base path is taken from config/RELEASE
+ If config does not exist, base path is taken from command
+ -d Verbose output (useful for debugging)
+
+Environment Variables:
+
+EPICS_MBA_DEF_APP_TYPE The application type you want to use as default
+EPICS_MBA_TEMPLATE_TOP The template top directory
+
+
+To create a new <top> issue the commands:
mkdir <top> # If <top> does not exist
cd <top>
- <base>/bin/<arch>/makeBaseApp [-e] <app> ...
-
-makeBaseApp does the following:
+ <base>/bin/<arch>/makeBaseApp -t <apptype> <app> ...
+ or
+ <base>/bin/<arch>/makeBaseApp -i -t <apptype> <ioc> ...
+makeBaseApp does the following:
+
+-
+EPICS_BASE is located
-
-If the user is in his/her home directory, makeBaseApp fails. This prevents
-the user from accidently cluttering up their home directory.
+If the -b option is specified it is used.
-
-EPICS_BASE is obtained from the command itself. This is why makeBaseApp
+If <top>/config/RELEASE exists and defines EPICS_BASE
+it is used.
+
+-
+It is obtained from the invocation of makeBaseApp. For this to work makeBaseApp
must be executed via a full path name to the makeBaseApp in the epics base
release you are using.
+
-
-If Makefile does not exist, it is created.
+TEMPLATE_TOP is located
+
+
+-
+If the -T option is specified it is used.
+
+-
+If <top>/config/RELEASE exists and defines TEMPLATE_TOP
+it is used.
+
+-
+If EPICS_MBA_TEMPLATE_TOP is defined it is used.
+
+-
+It is set equal to <epics_base>/templates/makeBaseApp/top
+
+
+-
+If -l is specified the list of application types is listed and makeBaseApp
+terminates.
+
+-
+If -i is specified and -a is not then the user is prompted for the
+ioc architecture.
+
+-
+The application type is determined.
+
+
+-
+If -t is specified it is used
+
+-
+If EPICS_MBA_DEF_APP_TYPE is defined it is used.
+
+-
+The application type is set equal to default.
+
+
+-
+If -i is specified Boot is appended to the application
+type otherwise App is appended.
+
+-
+If the application type is not in TEMPLATE_TOP makeBaseApp
+issues an error and terminates.
+
+-
+Two perl subroutines are defined
+
+
+-
+ReplaceFilename - This substitutes for the following in names of any file
+taken from the templates.
+
+
+-
+_APPNAME_
+
+-
+_APPTYPE_
+
+
+-
+ReplaceLine - This substitutes for the following in each line of each file
+taken from the templates.
+
+
+-
+_USER_
+
+-
+_EPICS_BASE_
+
+-
+_ARCH_
+
+-
+_APPNAME_
+
+-
+_APPTYPE_
+
+-
+_TEMPLATE_TOP_
+
+-
+_IOC_
+
+
+
+-
+If the application type directory has a file named Replace.pl it can replace
+the two perl subroutines.
+
+-
+If Makefile does not exist, it is created.
-
If directory config does not exist, then it and all the config
files are created.
-
-For each <app> that does not exist, it creates a directory and populates
-it as follows:
+If -i is specified
+
+-
+If directory iocBoot does not exist, it is created and the files from the
+template Boot directory are copied into it.
+
+-
+For each <ioc> specified on the command line a directory iocBoot/ioc<ioc>
+is created and populated with the files from the template.
+
+
+-
+If -i is NOT specified
+
+
+-
+For each <app> specified on the command line a directory <app>App
+is created and populated with the directory tree from the template.
+
+
+
+
+
+Application templates supplied
+with base
+
+
+
+
+
+EPICS base supplies the following sets of template files
+
+-
+exampleApp
+
+-
+exampleBoot
+
+-
+simpleApp
+
+-
+simpleBoot
+
+simpleApp creates an xxxApp with a Db and src directory. Each directory
+contains skeleton makefiles. simpleBoot creates an iocBoot directory and
+iocBoot/iocxxx directories. Each directory contains makefiles. The iocxxx
+directories also contain a skeleton st.cmd file.
+
+exampleApp and exampleBoot create a complete example application. It
+contains the following files.
+
<app>App
src/
- Makefile
- * Makefile.Host
- * Makefile.Vx
- * <app>Include.dbd
- * base.dbd
- * baseLIBOBJS
+ Makefile
+ Makefile.Host
+ Makefile.Vx
+ caExample.c
+ sncExample.st
+ xxxRecord.dbd
+ xxxRecord.c
+ devXxxSoft.c
+ <app>Include.dbd
+ base.dbd
+ baseLIBOBJS
Db/
- Makefile
-The user can rename Db to <anything>Db;
-
-If iocBoot or iocBoot/ioc<app> do not exist, they are created and populated
-as follows:
+ Makefile
+ dbExample.db
iocBoot
Makefile
+ nfsCommands
ioc<app>
- * Makefile
- * st.cmd
-The user can rename ioc<app> to ioc<anything>Db;
-
-If the -e option is specified the following files are created.
-
- <app>App
- Db/
- dbExample.db
- src/
- caExample.c
- sncExample.st
- xxxRecord.dbd
- xxxRecord.c
- devXxxSoft.c
+ Makefile
+ st.cmd
-The user is expected to edit (or possibly remove) the files marked with
-an "*". The directory Db can be renamed as long as the last two characters
-remain Db. Additional xxxDb directories can be created manually. After
-each xxxDb directory is created, the Makefile can be copied from another
-Db directory.
-The directory src can be renamed as long as the new name ends
-in Src. Additional source directories can be manually created.
-After each directory is created makefiles can be copied from another source
-directory and edited.
-
-
IMPORTANT: After creating new applications with makeBaseApp,
-<app>/iocBoot/ioc<app>/Makefile must be edited to specify the ioc
-architecture.
-
-
The remainder of this section gives a brief description of the files
-generated if makeBaseApp is executed with the -e option.
-
caExample.c
@@ -1033,20 +1247,38 @@ is:
# Example vxWorks startup file
#Following must be added for many board support packages
- #cd <full path to target bin directory>
+ #cd <full path to target bin directory>
+ < cdCommands
- ld < bin/iocCore
- ld < bin/xxxLib
- #ld < bin/seq
+ #< nfsCommands
- dbLoadDatabase("dbd/xxxApp.dbd")
- dbLoadRecords("xxxApp/xxxDb/xxx.db","user=USER")
+ cd appbin
+ ld < iocCore
+ ld < xxxLib
+ #ld < seq
+
+ cd startup
+ dbLoadDatabase("../../dbd/xxxApp.dbd")
+ dbLoadRecords("../../xxxApp/xxxDb/xxx.db","user=USER")
iocInit
#start sequence programs
#seq &sncxxx
+The cdCommands file defines vxWorks variables so that cd commands
+may be used later in the startup file.Definitions are provided for
+
+-
+appbin - A full path name to <top>/bin/<target_arch>
+
+-
+startup - A full path name to <top>/iocBoot/iocxxx
+
+-
+share - A full path name to share if SHARE is defined
+in <top>/config/RELEASE
+
The first ld command loads the core EPICS components. File xxxLib
is installed when gnumake is run in the <top>/xxxApp/src directory.
It contains the executable for all record, device, and driver support as
@@ -1054,10 +1286,10 @@ well as any other application specific object modules. If an IOC wants
to use support generated in a sub-application src directory, this statement
will have to be changed to coincide with the LIBNAME value.
-The dbLoadDatabase command loads the definitions of all menus, record
-types, device support, driver support, and breakpoint tables needed in
-this IOC. These are actually expanded files created by dbExpand and installed
-into dbd. If an application wants to use database definitions
+
The dbLoadDatabase command loads the definitions of all menus,
+record types, device support, driver support, and breakpoint tables needed
+in this IOC. These are actually expanded files created by dbExpand and
+installed into dbd. If an application wants to use database definitions
generated in a sub-application src directory, this statement will have
to be changed to coincide with the DBDNAME value.
@@ -1102,7 +1334,7 @@ The most useful commands at the top level directory are:
gnumake clean uninstall
-
This command removes everything created by make.
+
This command removes everything created or installed by make.
gnumake
@@ -1151,8 +1383,8 @@ and the make command is:
gnumake mv167
Another useful command is:
gnumake clean
-This removes the O. directories. ".<arch>" can be appended to invoke
-clean for a particular architecture.
+This removes the host and target architecture directories created by make.
+".<arch>" can be appended to invoke clean for a particular architecture.
xxxApp/xxxDb
@@ -1168,21 +1400,11 @@ The most useful command at this level is
gnumake
which is the same as issuing "gnumake" in each subdirectory of iocBoot.
-
-If the Makefile includes RULES.iocBoot then a file nfsCommands
-must exist in the iocBoot directory. Running make generates a
-file nfs.cmd, which contains everthing in the nfsCommands file
-in addition to a command to cd to the iocBoot directory. The st.cmd
-file in the iocxxx directory can then start with the commands:
-
< ../nfs.cmd
- cd "iocxxx"
-This provides an easy way to use NFS for all file access from the ioc.
-See the template files for examples.
iocBoot/iocxxx
-Executing gnumake in this directory creates soft links for use by the st.cmd
+Running gnumake in this directory creates the cdCommands
file.
@@ -1244,15 +1466,83 @@ subdirectory name
<top>/Makefile
This makefile performs a make in the xxxApp and iocBoot subdirectories.
-In addition it allows other top level make options described below. There
-is seldom need to modify this file.
+In addition it allows the top level make options uninstall and tar described
+in the previous section. There is seldom need to modify this file.
<top>/xxxApp/Makefile
This makefile just executes make in src and each *Db subdirectory.
<top>/xxxApp/src/Makefile.Host
-This file specifies Host components, which can be defined in Makefile.Host.
-Replace <arch_class> in the following by the specific architecture class.
+The following ioc related components can be built:
+
+-
+Breakpoint Tables
+
+-
+For each breakpoint table add the following definition
+
+ BPTS += <table name>.dbd
+
+-
+Record Support
+
+-
+For each new record type, the following definitions must be added to the
+makefile:
+
+
+ RECTYPES += <rectype>Record.h
+
+
+-
+and the record support files:
+
+
+
+<Record>Record.dbd
+
+
+
+-
+must exist.
+
+-
+If a menuXXX.dbd file is present, then add the following definition.
+
+ MENUS += menu<name>.h
+
+
+
+-
+Expanded Database Definition File
+
+Files containing database definition files are expanded by utility
+dbExpand and installed into <top>/dbd. The following variables are available.
+ DBDEXPAND += xxxInclude.dbd
+ DBDNAME = xxxApp.dbd
+ USER_DBDFLAGS += -I <include path>
+ USER_DBDFLAGS += -S <macro substitutions>
+
+ DBDINSTALL += xxx.dbd
+where:
+
+
+DBDEXPAND - A file containing database definitions.
+
+
+DBDNAME - The name of the file containing expanded definitions
+to be created and installed into <top>/dbd.
+
+
+USER_DBDFLAGS - Flags for dbExpand. Currently only an include
+path and macro substitution are supported.
+
+
DBDINSTALL - Installs the file into <top>/dbd.
+
+
+ Makefile.Host has many facilities for building host components..
+Replace <arch_class> in the following by the specific architecture class.
+
USR_CFLAGS C compiler flags for all systems
USR_CFLAGS_<arch_class> os-specific C compiler flags
USR_CFLAGS_DEFAULT C compiler flags for systems with no
@@ -1398,46 +1688,30 @@ MANIFEST
<top>/xxxApp/src/Makefile.Vx
The following components can be built:
--
-Breakpoint Tables
-
--
-For each breakpoint table add the following definition
-
- BPTS += <table name>.dbd
-
-
Record Support
-
For each new record type, the following definitions must be added to the
-makefile:
+makefile
-
- RECTYPES += <rectype>Record.h
- LIBOBJS += <rectype>Record.o
-
+
+ LIBOBJS += <rectype>Record.o
+
+-
+
-
and the record support files:
-
-<Record>Record.dbd
+
<Record>Record.c
-
-
must exist.
--
-If a menuXXX.dbd file is present, then add the following definition.
-
-
- MENUS += menu<name>.h
-
-
-
Device, Driver, other C modules
@@ -1471,37 +1745,14 @@ with the name specified by LIBNAME. If Makefile.Vx appears in
LIBNAME = xxxLib
LIBNAME_CXX = xxxLib
-The first is for c libraries and the second for c++ libraries.
-
--
-Expanded Database Definition File
-
-Files containing database definition files are expanded by utility
-dbExpand and installed into <top>/dbd. The following variables are available.
- DBDEXPAND += xxxInclude.dbd
- DBDNAME = xxxApp.dbd
- USER_DBDFLAGS += -I <include path>
- USER_DBDFLAGS += -S <macro substitutions>
-
- DBDINSTALL += xxx.dbd
-where:
-
-
-DBDEXPAND - A file containing database definitions.
-
-
-DBDNAME - The name of the file containing expanded definitions
-to be created and installed into <top>/dbd.
-
-
-USER_DBDFLAGS - Flags for dbExpand. Currently only an include
-path and macro substitution are supported.
-
-
-DBDINSTALL - Installs the file into <top>/dbd.
-
+
+The first is for c libraries and the second for c++ libraries.
+
+
+
+
State Notation Programs
@@ -1581,10 +1832,6 @@ INSTALL_DIR Installation directory (defaults to $(TOP))<
This makefile performs the following functions:
-
-Creates a soft link to the <top>/dbd directory.
-
-
This is useful for running database configuration tools in this directory.
--
creates xxx.db given xxx.template and xxx.substitutions
Thus given a template and a substitutions file, it creates a db file.
@@ -1601,17 +1848,22 @@ by the user:
NOTE: i is a positive integer
Note that the name of the substitutions file must be the same as the template
-except that "i" is appended to the file name.
+except that "i" is appended to the file name.
+
+Provides support for capfast
+
<top>/iocBoot/Makefile
This executes make in each subdirectory.
<top>iocBoot/iocxxx/Makefile
-This makefile creates soft links used in the st.cmd file. make
-sure that the definition:
+This makefile has a rule to generate cdCommands. Make sure that the definition:
ARCH = <arch>
refers to the correct architecture for your ioc processor.
+
+Since cdCommands is generated the user generated and/or modified files
+are independent of location even though cdCommands contains full path names.
CVS
@@ -1831,103 +2083,5 @@ can be imported into the repository via the command:
-
-
-TEMPLATES
-The following directory structure contains templates for Makefiles and
-for rules:
- iocsys/
- template/
- share/
- Makefile
- config/
- CONFIG
- CONFIG_APP
- RELEASE
- RULES.Db
- RULES.Host
- RULES.Vx
- RULES.ioc
- RULES_ARCHS
- RULES_DIRS
- RULES_TOP
- makeSoftLinks
- db/
- Makefile
- xxiocstatus.db
- xxxApp/
-
- top/
- Makefile
- config/
- CONFIG
- CONFIG_APP
- RELEASE
- RULES.Db
- RULES.Host
- RULES.Vx
- RULES.ioc
- RULES_ARCHS
- RULES_DIRS
- RULES_TOP
- xxxApp/
- Makefile
- src/
- Makefile
- Makefile.Host
- Makefile.Vx
- base.dbd
- baseLIBOBJS
- xxxDb/
- Makefile
- iocBoot/
- Makefile
- nfsCommands
- iocxxx/
- Makefile
- st.cmd
-A set of template files can be obtained via the WWW epics software distribution
-facility at APS.
-
-
-Multiple Top Level Applications
-APS/ASD manages its entire set of <top> level applications
-under a single directory structure:
- /usr/local/iocapps/
- CVSROOT/
- iocsys/
- <share releases>
- ascf/
- share/
- sharerf/
- linac/
- booster/
- par/
- parrf/
- boosterrf/
- srrf/
- srbpm/
- srfb/
- time/
- sitesys/
- sr/
-where
-
--
-ascf - directory for access configuration files.
-
--
-share- This, which is organized like a <top>, contains
-files that are shared between other <top> areas. The other
-areas actually uses releases of share just like they use releases of EPICS
-base.
-
--
-sharerf - Like share except for use by parrf, boosterrf, and srrf.
-
--
-linac, ..., sr are each <top> directories.
-
-