[root@root]# mkdir testIOC
[root@root]# cd testIOC
Enter the following commands in a position to make the IOC.
[root@root testIOC]# makeBaseApp.pl -t ioc testIOC
testIOC is an example IOC file in the /base/templates/makeBaseApp/top/.
Enter the name of the IOC that you made after the ioc.
[root@root testIOC]# ls
configure Makefile testIOCApp
And make iocBoot. Enter the name you want to do in 'Application name?'.
[root@root testIOC]# makeBaseApp.pl -i testIOC
Using target architecture linux-x86_64 (only one available)
The following applications are available:
testIOC
What application should the IOC(s) boot?
The default uses the IOC's name, even if not listed above.
Application name? testIOC
[root@root testIOC]# ls
configure iocBoot Makefile testIOCApp
Done!
Here is the tree structure of the IOC.
testIOC
├── configure
│ ├── CONFIG
│ ├── CONFIG_SITE
│ ├── Makefile
│ ├── RELEASE
│ ├── RULES
│ ├── RULES_DIRS
│ ├── RULES.ioc
│ └── RULES_TOP
├── iocBoot
│ ├── ioctestIOC
│ │ ├── Makefile
│ │ ├── README
│ │ └── st.cmd
│ └── Makefile
├── Makefile
└── testIOCApp
├── Db
│ └── Makefile
├── Makefile
└── src
├── Makefile
└── testIOCMain.cpp
[root@node2 testIOC]# makeBaseApp.pl -h
Usage:
<base>/bin/<arch>/makeBaseApp.pl -h
display help on command options
<base>/bin/<arch>/makeBaseApp.pl -l [options]
list application types
<base>/bin/<arch>/makeBaseApp.pl -t type [options] [app ...]
create application directories
<base>/bin/<arch>/makeBaseApp.pl -i -t type [options] [ioc ...]
create ioc boot directories
where
app Application name (the created directory will have "App" appended)
ioc IOC name (the created directory will have "ioc" prepended)
-a arch Set the IOC architecture for use with -i (e.g. vxWorks-68040)
If arch is not specified, you will be prompted
-b base Set the location of EPICS base (full path)
If not specified, base path is taken from configure/RELEASE
If configure does not exist, from environment
If not found in environment, from makeBaseApp.pl location
-d Enable debug messages
-i Specifies that ioc boot directories will be generated
-l List valid application types for this installation
If this is specified the other options are not used
-p app Set the application name for use with -i
If not specified, you will be prompted
-T top Set the template top directory (where the application templates are)
If not specified, top path is taken from configure/RELEASE
If configure does not exist, top path is taken from environment
If not found in environment, the templates from EPICS base are used
-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
-u user Set username; overrides OS defaults
Environment:
EPICS_MBA_DEF_APP_TYPE Application type you want to use as default
EPICS_MBA_TEMPLATE_TOP Template top directory
EPICS_MBA_BASE Location of EPICS base
Example: Create exampleApp
<base>/bin/<arch>/makeBaseApp.pl -t example example
<base>/bin/<arch>/makeBaseApp.pl -i -t example example
0 개의 댓글:
댓글 쓰기