Getting Help. NXP CodeWarrior Development Studio
Advertisement
Advertisement
Getting Help
The response file is parsed such that arguments are separated by whitespace except where surrounded by quote marks. Anything followed by a pound character
'#'
is used to indicate the rest of the line is a comment. Use
'\#'
in a response file if an argument actually starts with
'#'
.
The
@
option will make sure the response file content is used "as is", whereas a
@@ specification will ensure that environment variables in the response file contents are expanded. Note that only one level of environment variable expansion is performed.
Environment variable that expands to another variable-like syntax reamin unchanged. For example, in
FOO='$BAR'
,
$FOO
expands to
$BAR
, where as
$BAR
is not expanded.
Any of the following syntax can be used to recognize environment variables:
•
$[A-Za-z_][A-Za-z0-9_]*
•
$([A-Za-z_][A-Za-z0-9_]*)
•
${[A-Za-z_][A-Za-z0-9_]*}
Points to remember::
• The end of the environment variable is terminated when any char that is not a recognized environment variable token, is encountered.
• The
$
is escaped by a preceding
$
character in case of
@@
option.
• Lines in the response file should not exceed 64KB in length. It is recommended to put each option specified on a separate line, if many options are to be specified.
• A response file cannot have another response file i.e.,
@
and
@@
cannot be used inside a response file. For example: tool @argu.txt //Here all arguments and input files are passed in the file argu.txt
tool @argu.txt main.c // Here only arguments are passed in the file argu.txt
tool @@argu.txt
2.3 Getting Help
To show short descriptions of a tool's options, type this command at the command line:
tool -help
Where tool is the name of the CodeWarrior build tool.
To show only a few lines of help information at a time, pipe the tool's output to a pager program. For example,
CodeWarrior Development Studio for Power Architecture Processors Build Tools Reference Manual, Rev.
10.6, 02/2014
42 Freescale Semiconductor, Inc.
Chapter 2 Using Build Tools on the Command Line
tool -help | more
Will use the more
pager program to display the help information.
Enter the following command in a Command Prompt window to see a list of specifications that describe how options are formatted:
tool -help usage
Where tool is the name of the CodeWarrior build tool.
2.3.1 Parameter Formats
Parameters in an option are formatted as follows:
• A parameter included in brackets "
[]
" is optional.
• Use of the ellipsis "
...
" character indicates that the previous type of parameter may be repeated as a list.
2.3.2 Option Formats
Options are formatted as follows:
• For most options, the option and the parameters are separated by a space as in "
-xxx param
".
When the option's name is "
-xxx+
", however, the parameter must directly follow the option, without the "
+
" character (as in "
-xxx45
") and with no space separator.
• An option given as "
-[no]xxx
" may be issued as "
-xxx
" or "
-noxxx
".
The use of "
-noxxx
" reverses the meaning of the option.
• When an option is specified as "
-xxx | yy[y] | zzz
", then either "
-xxx
", "
-yy
", "
-yyy
", or "
-zzz
" matches the option.
• The symbols "
,
" and "
=
" separate options and parameters unconditionally; to include one of these symbols in a parameter or filename, escape it (e.g., as "
\,
" in mwcc file.c\,v)
.
CodeWarrior Development Studio for Power Architecture Processors Build Tools Reference Manual, Rev.
10.6, 02/2014
Freescale Semiconductor, Inc.
43
Download
Advertisement