Running MULTI from the command line

When you start MULTI, it attempts to use the host system windowing package by default. If you start MULTI on a color monitor, it defaults to color. If you start MULTI from a non-windowing monitor or if MULTI encounters problems with the window interface, it comes up in non-GUI mode. If MULTI is incorrectly coming up in non-GUI mode, check that the DISPLAY environment variable is set, or set it from the command line with the -display option.

If MULTI is in your path, then the command line syntax is:

multi [options] [filename]

If filename is a build file, then the Builder starts up with the build file loaded. Note that some options are specific to the Debugger and are not applicable to the Builder.

If filename is an executable program file that has had some (or all) of its component modules compiled for debugging (with Green Hills compiler's -G or -g options), then the Debugger starts up. For a list of command line options to use when opening the Debugger, see "Command line options".

If you specify a build file, it can either be a main project or a subproject. To open a subproject directly with the inherited options from a particular main project, specify the main project name followed by the subproject's name in quotes. For example:

multi "main.bld sub.bld"

This opens the subproject, sub.bld, with the options inherited from main.bld.

See the following table of examples.
How to open MULTI
Example Description
multi
The Builder is invoked on the last build file that was open.
multi default.bld
The Builder is invoked on default.bld. If default.bld is not found, MULTI will create it.
multi foo.bld
The Builder is invoked on the file foo.bld. The build file may be a main project or a subproject.
multi "parent.bld child.bld"
The Builder is invoked on the subproject child.bld directly with the inherited options from the main project parent.bld.
multi a.out
The Debugger is invoked on the executable a.out
multi -remote simppc
The Builder is invoked, and is connected to the simulator simppc. In this syntax, it is a function of the debug server whether the Builder window or the Debugger window is invoked. See the example below with multi -remote 5emon.
multi -remote simppc a.out
The Debugger is invoked on the executable a.out and the Debugger is connected to the simulator simppc.
multi -remote 5emon
The Debugger is invoked and is connected to the debug server 5emon. In this syntax, it is a function of the debug server whether the Builder window or the Debugger window is invoked. See the example above with multi -remote simppc.
multi foo.c
The Editor is invoked on the file foo.c.

Related topics:


Previous

Next



Copyright © 1999, Green Hills Software. All rights reserved.