User`s guide

64 Creating FPM Device Interface (XIF) Files
Using Long and Short Command Switch Forms
Most command switches come in long and short forms. The long form consists of the verbose, case-
sensitive name of the command, and it must be prefixed with a double dash '- -'. Long command
switches require a separator (a single space or the equals sign [=]) between the command switch and its
respective argument.
The short form consists of a single, case-sensitive, character that identifies the command, and it must
be prefixed with a single forward slash '/' or a single dash '-'. Optionally, short command switches may
be separated from their respective arguments with a separator (a single space or the equals sign [=]).
The following table demonstrates the long and short forms of the command switches you will typically
use to create XIFs.
Long Form Short Form
--source <file path> -n <file path>
--pid=<program ID> /i=<program ID>
--out=<destination path> /o<destination path>
-–basename=<file || filepath> /b <file>
Note: If no command switches or arguments follow the command name, the tool responds with usage
hints and a list of available command switches.
Other Command Switches
The following section lists the long and short forms of the other switches accepted by the libilon
command and describes the listed command switches.
Long Form
Short
Form Description
--help -? Display usage hint for the command
--file -@ Include a command file
--define -D Define a specified preprocessor
symbol (without value)
--defloc Location of an optional default
command file
--include -I Add the specified folder to the
include search path
--mkscript Generate command script in specified
location
--nodefaults Disable processing of default
command files
--silent Suppress banner message display
--verbosecomments -V Generate verbose comments
--verbose -v Run with one of the following
verbosity levels:
0(normal); 1(verbose); 2(trace)
--warning Display specified message type as a
warning