Environment Variables used by ObjecTime

Category |  Purpose |  Intended Audience |  Applicable to |  Description |  Limitations |  See also


Category:

Top

Toolset


Applicable to:

Top

All Versions


Purpose:

Top

To describe use of environment variables used by the ObjecTime toolset


Intended Audience:

Top

All users


Description:

Top

OBJECTIME_DOC

This environment variable tells ObjecTime where to find the ObjecTime on-line documentation. If you don't define this variable, ObjecTime will expect to find the documentation in $OBJECTIME_HOME/Documentation.

OBJECTIME_HOME

Set this environment variable to the location of the ObjecTime4.4.1 directory corresponding to your ObjecTime installation. Note that your ObjecTime session file should match the release against which you are running. That is, if you are working with ObjecTime 4.4.1 then your ObjecTime session should have ObjecTime4.4.1 in its title bar. You must also have $OBJECTIME_HOME/bin in your executable search path ($PATH and/or $path).

OBJECTIME_LIBRARY_MASK

When Absolute Library Paths is enabled it is possible to override the library naming convention for a library. The default convention is that which is used by UNIX linkers ('lib.a'). This can be overridden by setting the OBJECTIME_LIBRARY_MASK environment variable to the desired convention (searching mask) before starting the ObjecTime session. For example, for a library created from a MRI's librarian (lib68k) the mask would be:

    setenv OBJECTIME_LIBRARY_MASK '.lib'

This will cause the search to use this name mask, and also lead to the code generators outputting the library name in this fashion in the absolute path.

OBJECTIME_LICENSE_HOLDTIME

This environment variable determines how long the ObjecTime License Manager will hold a license for your use after you exit an ObjecTime session. This allows you to save your session, exit, and start up a session again in one consecutive action without worrying about losing your license token between the time you exit the session and the time you start up your next session. The value is specified in seconds and, if the environment variable is not specified, then the value 300 is used. Setting the value of this environment variable to zero ("0") will cause your license token to be returned to the pool immediately upon exiting ObjecTime.

OBJECTIME_LICENSE_SERVER

This environment variable must be set to the host name of the machine where your ObjecTime License Manager is running.

OBJECTIME_PARALLEL_MAKE_FLAGS

This environment variable is used when you've enabled the "Parallel Make" option in the "Specials" menu of the active compilation setup. The value of this environment variable is applied to subordinate "make" calls. Typically, the environment variable specifies the amount of parallelism desired in the "make". For example, a typical value when using "gmake" is "-j4". See the C++ User Guide and Reference, page 119, for more details.

OBJECTIME_VM

This specifies the Virtual Machine type used to run your ObjecTime session. Possible values include hp700, sun4, and sun5. This environment variable is automatically set by the "objectime" script with which you start your ObjecTime session and you should never have to set this variable yourself.

URTS_DEBUG

This controls the amount of debugging information you will see when you are running an ObjecTime MicroRTS executable. Setting it to zero ("0") will prevent the ObjecTime MicroRTS Debugger from starting and so you won't see the MicroRTS Debuffer prompt. The highest meaningful value for ObjecTime 4.4.1 is "20" which produces copious amounts of diagnostic output. In ObjecTime 5.0, this variable takes a list of debugger commands to execute on startup--you can use the debugger's "level" command to set the debug level on startup.


Limitations:

Top

CC

If set before OT started, it will be picked up by the default use of $CC in compilation setup.

Many places in ObjecTime where you enter pathnames will accept environment variables such as $PWD, $OBJECTIME_HOME, and so on as components of the pathname. However, beware the effects of changing such variables--they won't cause Compilation Unit Packages to be deemed to need recompiling, for example.


See also:

Top

None


 

Copyright © 1999, ObjecTime Limited.