TT_TYPE_COMP(1) — USER COMMANDS

NAME

tt_type_comp − The ToolTalk otype and ptype compiler

SYNOPSIS

tt_type_comp [-X] [-d {user|system|network}] -{p|O|P|h|v|{r type1..typeN}|{m|c|x} [-o ofile] file}

DESCRIPTION

tt_type_comp is the ToolTalk compiler for the otypes and ptypes provided in the specified typefile. The typefile is first run through cpp and then parsed and checked for correctness.

The compiler produces files for either the Classing Engine (the default) or an alternate xdr format. The default function of tt_type_comp when given a file containing definitions for ToolTalk otypes or ptypes is to merge the types in to the existing user database of types.

OPTIONS

−X Reset the default format from Classing Engine format to an xdr-based format.

−c Produce a Classing Engine format output file suitable for use with ce_db_merge or ce_db_build.

−d Specify the databse to work on which should be one of user (default), system, or network. For Classing Engine mode these are defined as:

user -- ~/.cetables/cetables

system -- /etc/cetables/cetables

network -- $OPENWINHOME/lib/cetables/cetables

For the xdr-base format these are defined as:

user -- ~/.tt/types.xdr

system -- /etc/tt/types.xdr

network -- $OPENWINHOME/tt/types.xdr

These three database form a hierarchy of database where the definition of a type in the user database overrides the definition in the system database and so on.

−h Print help on invoking tt_type_comp and exit.

−m Merge types into specified database. This is the default option. −p Print the ToolTalk types in the specified database. Types are printed out in source format suitable for recompilation with tt_type_comp.

−O Print out list of known otypes.

−P Print out list of known ptypes.

−ooutputfile
Output to the given file name.

...−rtype1
Remove the given ptypes or otypes from the database.

−s Silent mode. Don’t print out anything.

−x Produce a compiled XDR format type file.

−v Print out the version number and exit.

ENVIRONMENT

tt_type_comp will use the CEPATH variable for its definition of what where the databases are located. This variable should be a list of three components separated by :’s. Each component should be the name of the file to use:

<user_db>:<system_db>:<network_db>

Museum