Just a note of clarification - if I am on, say, Windows, I can take a cross platform example.kit (assuming that in fact I created it as cross-platform), specify a tclkit for Solaris, or HP/UX, Linux, MacOS X, etc. $mytclkit sdx.kit wrap $TCLScript.exe -runtime tclkitcopy.exe # where the name of the TCL-script is given without extension, # Creation of executables ("starpacks") that can run standalone starting from a TCL-script: To turn the example.tcl into a starkit on a Unixy system: On Unix, remember to change the permission modes of tclkit to be executable. On Unix, these may be installed as tclkit and sdx, while on Windows, these are more likely installed as tclkit.exe and sdx.kit. Install tclkit and make sure it's available in your PATH. The gui-version should be used when you specify the run-time tool in the final step when you link your script, otherwise your application will be silent too -). The command-line version is silent and does not produce pop-up screens, so it can be used to script the generation your executable. For Windows, download both the gui-version (e.g., ) and the command-line version (e.g., ).
#Timetool exe pdf
Read Beyond TclKit - Starkits, Starpacks and other *stuff pdf EPUB, by Steve Landersĭownload a tclkit for your platform. The process is straightforward enough that these instructions can be used with applications which involve several auxiliary files, extensions (but only stubsified ones?), and so on.
0 kommentar(er)
