LINUX RTAIÖÐ.runinfoÎļþÏê½â£¨Ó¢ÎÄ£©

Description of the "runinfo" format
-----------------------------------
Purpose of the "runinfo" files
------------------------------
"runinfo" files found in the source tree allow the "rtai-load" script
(see rtai-core/scripts/rtai-load) to retrieve the information it needs
to execute a RTAI application in an automated manner. This file
basically describes the module dependencies (i.e from standard RTAI
system modules) and the load/startup actions (i.e. insmoding module(s)
and/or launching executable(s)) that need to be taken to start a given
application.
This mecanism replaces the various hand-crafted "run" shell scripts
that existed up to RTAI's 24.1.12 (stromboli) version.
Format of a runinfo file
------------------------
All examples and tests contain/should contain an ASCII file called
runinfo that provides the needed information for having the
corresponding RTAI applications run through the "rtai-load"
script. This file is actually a template read by Autoconf's
"configure" script, where installation-dependent information is
automatically patched in, to produce the corresponding ".runinfo"
file. The "rtai-load" script will exclusively use .runinfo files to
find out the actions needed to bootstrap an application.
runinfo should list all possible execution targets for the given
example/test directory.
Each execution target appears on a single text line, contains four
specification fields separated by double-colons, and is parsed as:
target_name:module_dependencies:run_actions:init_comment
Therefore, having multiple targets in a single file is possible, like
this:
target_name1:module_dependencies_1:run_actions_1:init_comment_1
target_name2:module_dependencies_2:run_actions_2:init_comment_2
...
and so on.
o target_name is a symbolic name. The first line seen in a given file
stands for the default target.
o module_dependencies is a list defining the standard RTAI modules the
test/example depends on, and which must be loaded bef