2.4.2 Subcommand file usage

A subcommand file is a file that options and file names specified for a ccrl, asrl, rlink command are described.

The command treats the contents of a subcommand file as if they were command-line arguments.

Use a subcommand file when the arguments will not fit on the command line, or when same options are specified repeatedly each time the command is executed.

(1)

Using a subcommand file for the compiler and assembler

(a)

Cautions about description of a subcommand file

-

The arguments to be specified can be coded over several lines.
However, you cannot start a new line within the name of the option specification or file.

-

When the subcommand option is specified in a subcommand file, the same file name as the current subcommand file cannot be specified in the subcommand option.

-

The character code contents of a subcommand file cannot be specified by using the -character_set option.
If you use characters other than ASCII in the subcommand file, use the UTF-8 file with BOM.

-

The following characters are treated as special characters.
Special characters written in a subcommand file are deleted from the parameter string passed to the ccrl command, and the ccrl command is executed with that string.

" (double quotation mark)

The character string until the next double quotation mark is treated as a contiguous character string.

# (sharp)

If this is specified at the beginning of a line, the characters on that line before the end of the line are interpreted as a comment.

^ (circumflex)

The character immediately following this is not treated as a special character.

(b)

Example of subcommand file specification

Create subcommand file "sub.txt" using an editor.

-cpu=S2
-dev=dr5f100pj.dvf
-c
-D test
-I dir
-Osize

 

Specify sub.txt by subcommand file specification option "-subccomand" on the command line.

>ccrl -subccomand=sub.txt -ofile.obj file.c

 

The command line is expanded as follows.

>ccrl -cpu=S2 -dev=dr5f100pj.dvf -c -D test -I dir -Osize -ofile.obj file.c

(2)

Using a subcommand file for the optimizing linker

(a)

Cautions about description of a subcommand file

-

The leading hyphen ("-") on option names can be omitted.

-

A space can be used in place of the equals sign ("=") as the delimiter between the option and parameter.

-

A character string enclosed by double quotation marks (") can be specified as a file name or a path name.

-

A subcommand file should be written in the character code specified in the system locale.

-

Specify one option per one line.
If the command line cannot fit on a single line, you can use the ampersand ("&") to span multiple lines.

-

The subcommand option cannot be specified in a subcommand file.

[V1.03 or earlier]

-

When the subcommand option is specified in a subcommand file, the same file name as the current subcommand file cannot be specified in the subcommand option.

[V1.04 or later]

-

The following characters are treated as special characters.
These special characters themselves are not included in the command line of the rlink command and deleted.

& (and)

The following line will be treated as a continuation.

; (semicolon)

The characters on that line before the end of the line are interpreted as a comment.

(b)

Example of subcommand file specification

Create subcommand file "sub.txt" using an editor.

input file2.obj file3.obj       ; This is a comment.
library lib1.lib, &             ; This is a line continued.
lib2.lib

 

Specify sub.txt by subcommand file specification option "-subcommand" on the command line.

>rlink file1.obj -subcommand=sub.txt file4.obj

 

The command line is expanded as follows.

>rlink file1.obj file2.obj file3.obj -library=lib1.lib,lib2.lib file4.obj