C Environment Variables

Table Table C-1 lists and describes the environment variables used by FUSE tools. To see which environment variables are defined for the current FUSE session, start a Host Shell from any FUSE tool and use the printenv command in the Host Shell window.

Table C-1: Environment Variables Used by FUSE Tools

Environment Variable Name Tool Description

FUSE_TOP
All

The top-level directory under which FUSE is installed (/usr/opt/fuse). This is set at installation and should not be redefined.

FUSE_UID
All

The pathname of the directory containing the UID files for all FUSE windows.

HOME
All

The user's login directory. This variable should be defined after login.

DECMPP_FUSE_ENABLED
Builder

Optional. Adds default rules for .hpf.o and .mpl.o.

FUSE_CFRONT
Builder

Optional. Sets the makefile to use CC to compile C++ sources; otherwise sets cxx.

FUSE_PROJ_ROOT_DATA_DIR
Builder, C++ Class Browser, Call Graph Browser, Cross-Referencer, Database Manager

Points to the static analysis data directory. By default, this variable points to project_name.data in the project's data directory. If you change this variable to point to another location for the data directory, the FUSE tools automatically pick up the new location. For more information, see Chapter Chapter 11 and Appendix Appendix B.

FUSE_CM_POST_PROCESS
Code Manager

Allows setting of the postprocess value from an environment variable instead of from the Project Manager dialog box. This variable should be treated like a default value because any value specified in the Project Manager supersedes it.

FUSE_CM_PRE_PROCESS
Code Manager

Allows setting of the preprocess value from an environment variable instead of from the Project Manager dialog box. This variable should be treated like a default value because any value specified in the Project Manager supersedes it.

FUSE_MANAGER_REVISION _DEPTH
Code Manager

Allows setting of the default revision depth value from an environment variable instead of from Options: Application.

FUSE_EMACS
GNU Emacs

The pathname for GNU Emacs used by FUSE.

FUSE_XEMACS
XEmacs Editor

The pathname for XEmacs used in FUSE.

FUSE_MULE
Mule Editor

The pathname for Mule used in FUSE.

FUSE_VITERM
vi Editor

The pathname for vi used in FUSE.

FUSE_TERM
Host Shell

The terminal emulator you want to use, if you don't want to use the default emulator.

FUSE_HYPERHELP_FILE
HyperHelp

The location of the HyperHelp file for FUSE help. The default is $FUSE_TOP/rundata/hyperhelp/fuse.hlp.

FUSE_TUTORIAL_HYPERHELP_FILE
HyperHelp

The location of the HyperHelp file for FUSE tutorials. The default value is $FUSE_TOP/rundata/hyperhelp/fuse_tutorial.hlp.

HHPATH
HyperHelp

The location of the HyperHelp executable, usually $FUSE_BIN.

HOHPATH
HyperHelp

The location of the HyperHelp "help on help" file, hoh.hlp. The default is $FUSE_TOP/rundata/hyperhelp.

XPPATH
HyperHelp

The location of the HyperHelp print font information; the default value is $FUSE_TOP/rundata/hyperhelp/Xp.

FUSE_GPROF
Profiler

Optional. The pathname of gprof(1). If not defined, gprof will be run from the standard location. You should define this variable only if you installed gprof in a nonstandard location.

FUSE_PIXIE
Profiler

Optional. The pathname of pixie(1). If not defined, pixie will be run from the standard location. You should define this variable only if you installed pixie in a nonstandard location.

FUSE_AUXD
Profiler

Used to locate the AUXD files used by the Profiler.

FUSE_PIXIEPROF
Profiler

Optional. The pathname of prof(1) as used for analyzing pixie output. If not defined, prof -pixie will be run from the standard location. You should define this variable only if you installed prof in a nonstandard location.

SHELL
Profiler

Used to determine which shell to run. This variable is usually defined by the shell, so you should not have to define it. If for some reason this variable is not defined, the Profiler uses /usr/bin/csh.

FUSE_PROF
Profiler

Optional. The pathname ofprof(1), as used for analyzing non-pixie output. If not defined, prof will be run from the standard location. You should define this variable only if you installed prof in a non-standard location.

Environment Variable Name	Tool	Description
`FUSE_TOP`	All	The top-level directory under which FUSE is installed (`/usr/opt/fuse`). This is set at installation and should not be redefined.
`FUSE_UID`	All	The pathname of the directory containing the UID files for all FUSE windows.
`HOME`	All	The user's login directory. This variable should be defined after login.
`DECMPP_FUSE_ENABLED`	Builder	Optional. Adds default rules for `.hpf.o` and `.mpl.o`.
`FUSE_CFRONT`	Builder	Optional. Sets the makefile to use CC to compile C++ sources; otherwise sets `cxx`.
`FUSE_PROJ_ROOT_DATA_DIR`	Builder, C++ Class Browser, Call Graph Browser, Cross-Referencer, Database Manager	Points to the static analysis data directory. By default, this variable points to `project_name.data` in the project's data directory. If you change this variable to point to another location for the data directory, the FUSE tools automatically pick up the new location. For more information, see Chapter Chapter 11 and Appendix Appendix B.
`FUSE_CM_POST_PROCESS`	Code Manager	Allows setting of the postprocess value from an environment variable instead of from the Project Manager dialog box. This variable should be treated like a default value because any value specified in the Project Manager supersedes it.
`FUSE_CM_PRE_PROCESS`	Code Manager	Allows setting of the preprocess value from an environment variable instead of from the Project Manager dialog box. This variable should be treated like a default value because any value specified in the Project Manager supersedes it.
`FUSE_MANAGER_REVISION _DEPTH`	Code Manager	Allows setting of the default revision depth value from an environment variable instead of from Options: Application.
`FUSE_EMACS`	GNU Emacs	The pathname for GNU Emacs used by FUSE.
`FUSE_XEMACS`	XEmacs Editor	The pathname for XEmacs used in FUSE.
`FUSE_MULE`	Mule Editor	The pathname for Mule used in FUSE.
`FUSE_VITERM`	vi Editor	The pathname for vi used in FUSE.
`FUSE_TERM`	Host Shell	The terminal emulator you want to use, if you don't want to use the default emulator.
`FUSE_HYPERHELP_FILE`	HyperHelp	The location of the HyperHelp file for FUSE help. The default is `$FUSE_TOP/rundata/hyperhelp/fuse.hlp`.
`FUSE_TUTORIAL_HYPERHELP_FILE`	HyperHelp	The location of the HyperHelp file for FUSE tutorials. The default value is `$FUSE_TOP/rundata/hyperhelp/fuse_tutorial.hlp`.
`HHPATH`	HyperHelp	The location of the HyperHelp executable, usually `$FUSE_BIN`.
`HOHPATH`	HyperHelp	The location of the HyperHelp "help on help" file, hoh.hlp. The default is `$FUSE_TOP/rundata/hyperhelp`.
`XPPATH`	HyperHelp	The location of the HyperHelp print font information; the default value is `$FUSE_TOP/rundata/hyperhelp/Xp`.
`FUSE_GPROF`	Profiler	Optional. The pathname of `gprof(1)`. If not defined, gprof will be run from the standard location. You should define this variable only if you installed `gprof` in a nonstandard location.
`FUSE_PIXIE`	Profiler	Optional. The pathname of `pixie(1)`. If not defined, `pixie` will be run from the standard location. You should define this variable only if you installed `pixie` in a nonstandard location.
`FUSE_AUXD`	Profiler	Used to locate the AUXD files used by the Profiler.
`FUSE_PIXIEPROF`	Profiler	Optional. The pathname of `prof(1)` as used for analyzing `pixie` output. If not defined, `prof -pixie` will be run from the standard location. You should define this variable only if you installed `prof` in a nonstandard location.
`SHELL`	Profiler	Used to determine which shell to run. This variable is usually defined by the shell, so you should not have to define it. If for some reason this variable is not defined, the Profiler uses `/usr/bin/csh`.
`FUSE_PROF`	Profiler	Optional. The pathname of`prof(1)`, as used for analyzing non-pixie output. If not defined, `prof` will be run from the standard location. You should define this variable only if you installed `prof` in a non-standard location.