Previous: Running gnatstub, Up: Creating Sample Bodies Using gnatstub

25.2 Switches for gnatstub

If the destination directory already contains a file with the name of the body file for the argument spec file, replace it with the generated body stub.
Put the comment header (i.e., all the comments preceding the compilation unit) from the source of the library unit declaration into the body stub.
Put a sample comment header into the body stub.
Use the content of the file as the comment header for a generated body stub.
These switches have the same meaning as in calls to gcc. They define the source search path in the call to gcc issued by gnatstub to compile an argument source file.
This switch has the same meaning as in calls to gcc. It defines the additional configuration file to be passed to the call to gcc issued by gnatstub to compile an argument source file.
(n is a non-negative integer). Set the maximum line length in the body stub to n; the default is 79. The maximum value that can be specified is 32767. Note that in the special case of configuration pragma files, the maximum is always 32767 regardless of whether or not this switch appears.
(n is a non-negative integer from 1 to 9). Set the indentation level in the generated body sample to n. The default indentation is 3.
Order local bodies alphabetically. (By default local bodies are ordered in the same way as the corresponding local specs in the argument spec file.)
Same as -gnatyn
Do not remove the tree file (i.e., the snapshot of the compiler internal structures used by gnatstub) after creating the body stub.
Same as -gnatyMn
void raising PROGRAM_ERROR in the generated bodies of program unit stubs. This is not always possible for function stubs.
Do not place local comment header with unit name before body stub for a unit.
-o body-name
Body file name. This should be set if the argument file name does not follow the GNAT file naming conventions. If this switch is omitted the default name for the body will be obtained from the argument file name according to the GNAT file naming conventions.
Quiet mode: do not generate a confirmation when a body is successfully created, and do not generate a message when a body is not required for an argument unit.
Reuse the tree file (if it exists) instead of creating it. Instead of creating the tree file for the library unit declaration, gnatstub tries to find it in the current directory and use it for creating a body. If the tree file is not found, no body is created. This option also implies -k, whether or not the latter is set explicitly.
Overwrite the existing tree file. If the current directory already contains the file which, according to the GNAT file naming rules should be considered as a tree file for the argument source file, gnatstub will refuse to create the tree file needed to create a sample body unless this option is set.
Verbose mode: generate version information.