Dynamically Linking Windows Interpreters
To create a dynamically-linked Tcl application under Windows, you link your application with export libraries, which have a .lib extension. At run-time, your application loads the dynamic library corresponding to that export library, which has the same name as the export library but a .dll extension. You don't need the .lib file at run-time.
You link your application with the appropriate Tcl library and, if needed, the appropriate Tk library. You don't need to link with any other Tcl extension libraries; your application loads the dynamic libraries for any other extensions as needed at run-time. You must also link with any other application-specific libraries your application might use (for example, custom driver software for interacting with a special peripheral device).
The TclPro Windows libraries are located in subdirectories of win32-ix86 in the TclPro installation directory. Table 17 lists the dynamic libraries shipped and their corresponding locations.
Note that TclPro uses the convention of ending the name of a library that was built with debugging options with the letter "d." For example, Tcl83d.dll is the Tcl DLL built with debugging turned on and Tcl83d.lib is its export library. The "d" libraries were all built with the /MDd flag, the others with /MD.
If you use the debug libraries, also link your application with MSVCRTD.LIB; otherwise link it with MSVCRT.LIB.
http://www.ajubasolutions.com Voice: (650) 210-0100 Fax: (650) 210-0101 support@ajubasolutions.com |