Statically Linking Unix Interpreters

---

To create a statically-linked Tcl application under Unix, you link your application with the static version of the Tcl library and, if needed, the Tk library. You also must link with all other Tcl extension libraries used by your application, and any other application-specific libraries your application might use (for example, custom driver software for interacting with a special peripheral device). Unlike Windows, there are no separate debug and non-debug libraries.

All of the Unix libraries shipped with TclPro are located in subdirectories of the TclPro installation directory. The libraries are organized by platform, with directory names as shown in Table 14. Table 16 lists the static libraries shipped for Unix systems.

Table 16 Unix Libraries for Static Linking 

Unix Library	Description
libtcl8.3.a	Tcl static library
libtk8.3.a	Tk static library
libtbcload13s.a	tbcload static library
libitcl32s.a	[incr Tcl] static library
libitk32s.a	[incr Tk] static library
libtclx8.3.a	TclX static library
libtkx8.3.a	TkX static library
libexpect5.32.a	Expect static library

Note: The IRIX libraries are compiled with the n32 flag.

Note that many of the static libraries end with the letter "s"; this is especially useful in that it eliminates some ambiguities in the interpretation of l linker flags. For example, ltbcload13 refers to the shared library implementation of tbcload, whereas ltbcload13s refers to the static version. If the "s" convention were not used, the l flag for either would be ltbcload13, and which one of the two libraries is used for the linking would depend on the resolution rules currently active in the linker.

http://www.ajubasolutions.com Voice: (650) 210-0100 Fax: (650) 210-0101 support@ajubasolutions.com