next up previous contents index
Next: Log Files and Error Up: Starting Xic Previous: Xic Search Paths   Contents   Index


Initialization Files

When Xic is started, a number of files are read. This section describes these files, and the order of access. None or these files is required to exist.

As the program starts and the graphics is initialized, the X window system may access various files for resource resetting. See the X documentation for details. The attribute (non-layer) colors used in Xic can be set through the resource mechanism (see A.2).

Next, an ``.xicinit'' initialization script, if present, will be read and executed. The initialization script uses exactly the same format as other script files, as are normally found along the script search path. The scripting language is described in detail in Chapter 12. The script can set user preferences or otherwise modify Xic. Since this file is read before other files, it can be used to set the search paths used to find other startup files, in particular the technology file. The base name for the script is ``.xicinit'', and the same extension as the technology files can be present. If, for example, Xic is started with an extension ``.ext'' (-Text given on the command line), Xic will look for files ./.xicinit.ext and $HOME/.xicinit.ext, then ./.xicinit and $HOME/.xicinit, in that order, where ``$HOME'' indicates the user's home directory. The first file found will be executed. If Xic is started without a technology file extension, only the script files without an extension will be executed.

If a file named ``xic_font'' is found in the library search path, the file is read to obtain the text font used for on-screen label text.

If a file named ``xic_logofont'' is found in the library search path, the file is read to obtain the text font used for the logo (physical text) command.

If a key mapping file is found in the library search path, that file is read to provide a mapping for certain keyboard keys which may not be mapped as expected. This file is generated from within Xic with the Key Map command, and is not normally edited by the user.

If a technology file is being used, Xic will read the file at this point, before reading the user's script and macro files (below).

Next, Xic will attempt to read a file with the base name ``.xicmacros'', and the same extension as the technology files can be present. If, for example, Xic is started with an extension ``.ext'' (-Text given on the command line), Xic will look for files ./.xicmacros.ext and $HOME/.xicmacros.ext, then ./.xicmacros and $HOME/.xicmacros, in that order, where ``$HOME'' indicates the user's home directory. The first file found will be read. If Xic is started without a technology file extension, only the script files without an extension will be read. This file holds macro definitions which are mapped to key presses, as generated by the Key Map command in the Attributes Menu. The .xicmacros file is rarely if ever directly edited by the user.

Next, an initialization script, if present, will be read and executed. The initialization script uses exactly the same format as other script files, as are normally found along the script search path. The script can set user preferences or otherwise modify Xic, and, unlike the similar ``.xicinit'' file, performs these commands after the technology file has been read. The base name for the script is ``.xicstart'', and the same extension as the technology files can be present. If, for example, Xic is started with an extension ``.ext'' (-Text given on the command line), Xic will look for files ./.xicstart.ext and $HOME/.xicstart.ext, then ./.xicstart and $HOME/.xicstart, in that order, where ``$HOME'' indicates the user's home directory. The first file found will be executed. If Xic is started without a technology file extension, only the script files without an extension will be executed.

The legal message is read from a file named ``xic_mesg'' found in the library search path. This message appears when the About button in the Help Menu is selected.

As needed, Xic will also read the device.lib file, search and map the device models and help files, and open the first command line file for editing. The device.lib file supplies the device templates used in electrical mode. The model files provide SPICE models used for generating SPICE output. These files are read the first time access is required.

The xic_stipples file is read, which initializes the default fill pattern registers in the fill pattern editor in the Attributes Menu. Like the device and model libraries, the technology file, font files, etc., the library search path is used to locate this file.

On installation, a default configuration is provided for Xic. The user will need to reconfigure Xic for their requirements. This reconfiguration is accomplished primarily by editing a custom technology file, which Xic reads on startup, and also by possibly setting some of the environment variables before starting Xic. These variables can be set in the user's shell startup file, as appropriate for the user's operating system.

The technology file contains all of the information Xic needs for physical layout, plus information on hard copy support, printer commands, and the like. It also provides values for a number of presentation attributes including the colors used on-screen. The default technology file, plus several other files needed, are placed in a system-wide location on installation, usually /usr/local/lib/xictools/xic/startup. This directory is typically set to be read-only, thus the user must establish an alternative location in their own directory tree for customized startup files. The default technology file provided with Xic is for generic MOSIS scalable CMOS.

The Save Tech button in the Attributes Menu creates an updated copy of the technology file in the current directory. Most of the changes to an existing technology file can be performed from within Xic, though some text editing may be required on occasion. The technology file format is described in the Appendix.


next up previous contents index
Next: Log Files and Error Up: Starting Xic Previous: Xic Search Paths   Contents   Index
Stephen R. Whiteley 2006-10-23