Name

til − Compile Tool Integration Language file

Syntax

til [ option ...] [ file ...]

Description

The til command invokes the Tool Integration Language (TIL) compiler.  The TIL compiler and Message Monitor tool are the basic components of EnCASE, programming facilities for integrating a non-FUSE tool into FUSE with a minimum of program modification.

The Tool Integration Language specifies the following information about a non-FUSE tool so that it can operate in FUSE:

•The tool’s name and startup key combination so that it can be listed on the FUSE Control Panel

•The tool’s startup specifications so that it can be initialized and started from FUSE

•The tool’s states and messages so that it can send and receive messages in FUSE and interoperate with FUSE tools

You specify this information in a file with a .til extension (TIL file).  The til command processes each file with the C preprocessor, cpp, and the TIL compiler to produce the following, based on selected options:

•TIL file syntax error diagnostics

•C language and C header files (.c and .h files) of tool messaging functions that were written with the EnCASE C or script interface

•A new script (the tools.rc file) to be used by the FUSE Control Panel, which integrates non-FUSE tool information (tool name and startup specifications) with FUSE tool information

•A new FUSE message schema (the fuseschema.msl file), which integrates all non-FUSE tool messaging with FUSE tool messaging

If you do not specify any options or files, the TIL compiler generates error diagnostics, a startup script, and a message schema for all tools with TIL files and places these files in the working directory.  The new startup script and schema do not replace what is currently being used by FUSE. 

Arguments

The file argument specifies one or more TIL files to be compiled.  Any files you specify are added to the set of TIL files for FUSE tools in the $FUSE_TOP/rundata/schema directory. The $FUSE_TOP environment variable is defined according to where FUSE is installed, which for most installations is /usr/opt/FUSnnn (where nnn is 400 for FUSE V4.0).

Options

−aclass [-aclass]... 
Specifies that the tool is active.  An active tool is listed in and can be started from FUSE Tools menus. When this option is specified, it supercedes the active value declared in the TIL file.

The name specified for class must match the tool-name value declared for the class attribute in the TIL file.

−cclass [-cclass]... 
Generates C language files (.c and .h files) for the messaging functions for the specified class (tool). You must specify this option to generate the C files for linking with the FUSE message files.  You can specify more than one class.

The name specified for class must match the tool-name value declared for the class attribute in the TIL file.

−dclass [-dclass]... 
Specifies that the tool is inactive.  An inactive tool is not listed in and cannot be started from FUSE Tools menus until the Modify Tools... item (on the Control Panel Tools menu) is used to move it from the Inactive list to the Active list. When this option is specified, the file fuse.rc, which is generated after using the Modify Tools item, must be in the user’s home directory and it supercedes the active value declared in the TIL file.

The name specified for class must match the tool-name value declared for the class attribute in the TIL file.

−Dname [-Dname]... 
Defines name as if by a #define directive.  The −D option is superceded by a −U option that specifies the same name.

−install
Starts a complete build of the FUSE message schema, using files in the $FUSE_TOP/rundata/schema directory.   The current FUSE message schema will be replaced with the new schema.

When this option is specified, the build must be run from a privileged account. 

Do not use this option until the new tool has been completely debugged and tested with FUSE. 

When this option is specified, any files specified on the command line, and the −no_schema, −no_ansi, or −c options are ignored.

−Idir [-Idir]... 
Specifies the pathname for header files and TIL files to be used in addition to the default header and TIL files. You can specify more than one pathname. If this option is not specified, first the working directory and then the $FUSE_TOP/rundata/schema directory is searched.

−no_ansi
Indicates that the C compiler being used to compile the tool’s source code is not ANSI-C compliant; therefore, to avoid compilation errors, all parameters in the function prototypes are commented out.

−no_schema
Specifies that only C files for the messaging functions are generated for the tool.  The startup script and message schema are not generated.  If you do not specify this option, a new startup script (the tools.rc file) and message schema (the fuseschema.msl file) are generated in the working directory. The startup script and message schema do not replace those currently being used by FUSE from the $FUSE_TOP/rundata/schema directory.

The −no_schema option is ignored if the −install option is specified.

−syntax
Specifies that only error-checking on the TIL file is done.  C files, startup script, and the message schema are not generated.

−Uname [-Uname]... 
Removes the definition of name.  The −U option supercedes a −D option that specifies the same name.

Examples

To generate just error diagnostics for two tool classes, tool1 and tool2 in one TIL file, issue this command: % til -syntax tools.til

To generate C files without the startup script and message schema, issue this command: % til -ctool1 -ctool2 -no_schema tools.til

To generate C files, a startup script, and a message schema, issue this command: % til -ctool1 -ctool2 tools.til

To generate a new startup script and message schema and replace the script and schema used by FUSE, issue this command from a privileged account: % til -install

See Also

cpp(1), fuse(1), fusescript(1)

DEC FUSE EnCASE Manual

DEC FUSE Handbook

Ladebug Debugger Manual: Window and Command-Line Interface